Navigation Peek Ahead and Behind in a Navigation Application

ABSTRACT

A method of providing a sequence of turn-by-turn navigation instructions on a device traversing a route is provided. Each turn-by-turn navigation instruction is associated with a location on the route. As the device traverses along the route, the method displays a turn-by-turn navigation instruction associated with a current location of the device. The method receives a touch input through a touch input interface of the device while displaying a first turn-by-turn navigation instruction and a first map region that displays the current location and a first location associated with the first turn-by-turn navigation instruction. In response to receiving the touch input, the method displays a second turn-by-turn navigation instruction and a second map region that displays a second location associated with the second turn-by-turn navigation instruction. Without receiving additional input, the method automatically returns to the display of the first turn-by-turn navigation instruction and the first map region.

INCORPORATION BY REFERENCE; DISCLAIMER

Each of the following applications are hereby incorporated by reference:application Ser. No. 15/466,485 filed on Mar. 22, 2017; application Ser.No. 15/207,476 filed on Jul. 11, 2016; application Ser. No. 14/055,811filed on Oct. 16, 2013; application No. 61/832,838 filed on Jun. 8,2013. The Applicant hereby rescinds any disclaimer of claim scope in theparent application(s) or the prosecution history thereof and advises theUSPTO that the claims in this application may be broader than any claimin the parent application(s).

BACKGROUND

Many map-based applications available today arc designed for a varietyof different devices (e.g., desktops, laptops, tablet devices,smartphones, handheld global positioning system (GPS) receivers, etc.)and for various different purposes (e.g., navigation, browsing, sports,etc.). Most of these applications generate displays of a map based onmap data that describes relative locations of streets, highways, pointsof interest, etc., in the map. Some map-based applications provide anavigation feature, which provides the user with turn-by-turninstructions to a destination. Most of these applications, however, donot have sophisticated features that today's demanding users wish tohave in their map-based applications.

BRIEF SUMMARY

Some embodiments of the invention provide a navigation application thatallows a user to peek ahead a future turn-by-turn navigation instructionand a turn-by-turn map view of a location that corresponds to the futurenavigation instruction while the navigation application guides the userthrough a route. In some embodiments, the navigation applicationdisplays in a display area a different turn-by-turn navigationinstruction and a different turn-by-turn map view of a differentlocation that corresponds to the different turn-by-turn navigationinstruction according to the user's current position that changes as theuser moves along the route. The navigation application allows the userto slide out a currently displayed turn-by-turn navigation instructionfrom the display area to slide in a future turn-by-turn navigationinstruction. As the future turn-by-turn navigation instruction slidesin, the navigation application displays in the display area a locationthat corresponds to the future turn-by-turn navigation instruction.

In some embodiments, the navigation application provides oneturn-by-turn navigation instruction at a time for the user to follow.The navigation application of some embodiments presents the turn-by-turnnavigation instruction in a banner that resembles a road sign, byoverlaying the banner on a map view that shows a region of the map inwhich the user is currently positioned. As the user makes progresstowards the destination of the route, the navigation application updatesthe map view to show different regions of the map in which the user'schanging current position falls. This map view for providing the currentturn-by-turn navigation instruction is referred to as a navigation view.The navigation application displays a map view in a display area of thenavigation application.

The navigation application of some embodiments allows the user to peekahead the future navigation instructions before the user advances on theroute to the regions of the map that correspond to the future navigationinstructions. Specifically, the navigation application allows the userto slide out the banner that displays the current navigation instructionfrom the display area of the navigation application. As the banner forthe current navigation instruction slides out of the display area, thenavigation application slides another banner that displays the nextnavigation instruction into the display area. In addition, thenavigation application modifies the map view to show the location forthe next navigation instruction in the display area without dropping outthe current position of the user from the display area. The location forthe next navigation instruction is a location in the map where the useris to make a maneuver (e.g., a left turn) according to the nextnavigation instruction e.g., “Turn left onto Main Street”).

When the user slides out the banner for the next navigation instruction,the navigation application slides in another banner that displays anavigation instruction that is after the next navigation instruction inthe sequence of navigation instructions for the route. The navigationapplication then changes the map view further to display the locationfor this navigation instruction and the location for the next navigationinstruction as well as the current position of the user in the displayarea. In this manner, the navigation application allows the user to peekahead the future navigation instructions up to the last navigationinstruction for the route. The modified map view that shows thelocations of the future navigation instructions and the current positionof the user is referred to as a peek view.

For displaying a peek view, the navigation application of someembodiments make a direction, from the current location of the user tothe location for a particular future navigation instruction, point tothe top side of the screen of the device when a banner for theparticular future navigation instruction is displayed in the screen. Inorder to make the direction to point to the top side of the screen whiledisplaying both the current location and the location for the particularfuture navigation instruction in the display area, the navigationapplication zooms out, pans and/or rotates the map.

The navigation application of some embodiments also allows the user topeek behind the past navigation instructions. Specifically, thenavigation application slides in a banner that displays the previousnavigation instruction when the user slides out the banner that displaysthe current navigation instruction in a different direction than thedirection in which the user slides out the banner to peek ahead thefuture navigation instructions. As the banner for the previousnavigation instruction slides in, the navigation application modifiesthe map view to show the location for the previous navigationinstruction in the screen without dropping out the current position ofthe user from the display area. In this manner, the navigationapplication of some embodiments allows the user to peek behind the pastnavigation instructions up to the first navigation instruction of theroute.

Different embodiments allow the user to slide out a banner from thedisplay area differently. For instance, the navigation application ofsome embodiments allows the user to swipe the screen horizontally (e.g.,to the left or to the right) to slide the banner out of the displayarea. Alternatively or conjunctively, the navigation application of someembodiments allows the user to swipe the screen vertically (e.g., swipeup or swipe down) to slide out the banner to either side out of thedisplay area. In some embodiments, the navigation interprets a swipe asa horizontal swipe even when the swipe is not perfectly parallel to ahorizontal line of the display area, as long as the swipe makes an anglewith the horizontal line that is within a threshold angle. Likewise, thenavigation interprets a swipe as a vertical swipe even when the swipe isnot perfectly parallel to a vertical line of the display area as long asthe swipe makes an angle with the vertical line that is within thethreshold angle.

In some embodiments, the navigation application takes the horizontalswipes to move the banners when the navigation application presentsnavigation instructions for a walking route. The navigation applicationtakes vertical swipes to move the banner when the navigation applicationpresents navigation instructions for a driving route.

In some embodiments, the navigation application reverts back to anavigation view from a peek view when the touch, which has caused thenavigation application to modify the map view to display the peek view,is off the display area. For instance, when the user touches the displayarea with a finger and moves the finger on the display area withoutlifting up the finger, the navigation application of some embodimentsmoves the banner for the current navigation instruction accordingly andalso modifies the map view to display the peek view. However, thenavigation application of some of these embodiments reverts back to thenavigation view as soon as the touch is not maintained with the displayarea.

In other embodiments, the navigation application keeps displaying thepeek view even when the touch is not maintained with the display area.In these embodiments, the navigation application reverts back to thenavigation view from the peek view when the user swipes the screen againto cause the navigation application to slide in the banner that displaysthe current navigation instruction back to the screen.

In some of these embodiments, the navigation application automaticallyreverts back to the navigation view from the peek view without receivingany swipes. For instance, in some embodiments, the navigationapplication keeps track of the current position of the user while thenavigation application is displaying the peek view. When the currentposition of the user advances to a location that is within a thresholddistance from the location for the current navigation instruction, thenavigation reverts back to the navigation view for the currentnavigation instruction. Alternatively or conjunctively, the navigationapplication of some embodiments keeps track of the time since thenavigation application started displaying the peek view and reverts tothe navigation view when a defined period of time elapses since thestart of the peek view display.

The preceding Summary is intended to serve as a brief introduction tosome embodiments of the invention. It is not meant to be an introductionor overview of all inventive subject matter disclosed in this document.The Detailed Description that follows and the Drawings that are referredto in the Detailed Description will further describe the embodimentsdescribed in the Summary as well as other embodiments. Accordingly, tounderstand all the embodiments described by this document, a full reviewof the Summary, Detailed Description and the Drawings is needed.Moreover, the claimed subject matters are not to be limited by theillustrative details in the Summary, Detailed Description and theDrawings, but rather are to be defined by the appended claims, becausethe claimed subject matters can be embodied in other specific formswithout departing from the spirit of the subject matters.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth in the appendedclaims. However, for purposes of explanation, several embodiments of theinvention are set forth in the following figures.

FIG. 1 illustrates an example of an navigation application that switchesfrom the driving mode to the pedestrian mode and then switches back tothe driving mode.

FIG. 2 illustrates that the navigation application of some embodimentsbounces a banner back to its original position.

FIG. 3 illustrates that the navigation application of some embodimentsallows a user to peek behind the previous navigation instructions for aroute being traveled by the user.

FIG. 4 illustrates an example of the navigation application of someembodiments that follows the movement of the touch on the screen inorder to change the map view smoothly as the touch on the screen moves.

FIG. 5 conceptually illustrates a process that the navigationapplication of some embodiment performs to present the navigation viewfor the current navigation instruction of a route and a peek view forthe previous or next navigation instruction of the route.

FIG. 6 illustrates that the navigation application backs out from a peekview for the next navigation instruction of a route to a navigation viewfor the current navigation instruction of the route.

FIG. 7 illustrates a situation in which the navigation application ofsome embodiments automatically reverts to the navigation view for thecurrent navigation instruction from the peek view for the nextnavigation instruction

FIG. 8 conceptually illustrates a process that the navigationapplication of some embodiment performs to revert automatically to thenavigation view for the current navigation instruction of a route beingtraveled by a user.

FIG. 9 illustrates an example of the navigation application that allowsa user to peek ahead the next navigation instructions for a route thatis being presented in the driving mode.

FIG. 10 illustrates that the navigation application of some embodimentsbounces a banner back to its original position.

FIG. 11 illustrates that the navigation application of some embodimentsallows a user to peek behind the previous instructions for a route thatis being presented in the driving mode.

FIG. 12 conceptually illustrates a process that the navigationapplication in the driving mode performs to present the navigation viewfor the current navigation instruction of a route and a peek view forthe previous or next navigation instruction of the route.

FIG. 13 illustrates that the navigation application of some embodimentsbacks out from a peek view for the next navigation instruction of aroute being traveled by a user and automatically reverts to a navigationview for the current navigation instruction of the route.

FIG. 14 illustrates another situation in which the navigationapplication of some embodiments automatically reverts to the navigationview for the current navigation instruction of a route from the peekview for the next navigation instruction of the route.

FIG. 15 illustrates example architecture of a navigation applicationthat allows the user to peek ahead and behind a route.

FIG. 16 is an example of an architecture of a mobile computing device ofsome embodiments.

FIG. 17 conceptually illustrates an example of an electronic system withwhich some embodiments of the invention are implemented.

FIG. 18 illustrates a map service operating environment, according tosome embodiments.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerousdetails, examples, and embodiments of the invention are, set forth anddescribed. However, it will be clear and apparent to one skilled in theart that the invention is not limited to the embodiments set forth andthat the invention may be practiced without some of the specific detailsand examples discussed.

The navigation application of some embodiments is part of an integratedmapping application that includes several useful modalities, includinglocation browsing, map searching, route identifying and route navigatingoperations. This integrated application (referred to above and below asthe mapping application, the navigation application, or the integratedapplication) in some embodiments is defined to be executed by a devicethat has a touch-sensitive screen and/or a near-touch sensitive screenthat displays the output of the application. In some embodiments, thisdevice has a multi-touch interface for allowing a user to provide touchand gestural inputs through the screen to interact with the application.Examples of such devices are smartphones (e.g., iPhone● sold by AppleInc., phones operating the Android● operating system, phones operatingthe Windows● operating system, etc.) tablet computers (e.g., iPad● soldby Apple Inc., tablets operating the Android● operating system, tabletsoperating the Windows● operating system, etc.), laptop computers,desktop computers, etc.

The navigation application of some embodiments provides multipledifferent views during navigation and smooth transitions between theseviews. In some embodiments, examples of such views include atwo-dimensional (2D) turn-by-turn view, a three-dimensional (3D)turn-by-turn view, and an overall route view. The application in someembodiments generates the turn-by-turn views from a perspectiverendering position within a 3D navigation scene that the device renders.This perspective rendering position in some embodiments is adjustableand can be viewed as a virtual camera that can capture the 3D navigationscene from a variety of different perspectives (e.g., from a variety ofdifferent positions and orientations). Accordingly, in some embodiments,the turn-by-turn navigation is an animated rendering of navigated routethat is rendered from the vantage point of a virtual camera thattraverses along the direction of the route based on the traversaldirection and speed of the user carrying the device, which in someembodiments is captured by directional data (e.g., GPS data,triangulated cell-tower data, etc.) associated with the device.

Some embodiments provide a navigation application that allows a user topeek ahead/behind to future/previous navigation instructions for a routebeing navigated by the user. For example, the navigation application mayprovide a zooming function, which leaves the user's current position onthe screen of the device, but allows the user to see future navigationinstructions. The navigation application may maintain the zoomed outview, slowly zooming in as the user approaches the locations for thecurrent navigation instruction. Alternatively, the peek view may be atemporary view that automatically reverts to the navigation view after adefined period of time.

The navigation application may provide a similar function for peeking atprevious directions without re-orienting the map. For example, thenavigation application may display a previous navigation instruction bymoving the current location further up the screen to fit both thelocation for the previous navigation instruction and the location forthe current navigation instruction on the screen.

The navigation application of different embodiments differently obtainsa route between a starting location and an ending location. In someembodiments, the navigation application computes the route locally atthe device on which the navigation application runs. Alternatively orconjunctively, the navigation application sends the information aboutthe starting and ending locations to a remote server, which computes theroute and returns the computed route back to the device and thenavigation application. In some embodiments, a compute route includes aset of navigation instructions that guides the user traveling on theroute from the starting location to the ending location. A navigationinstruction is also referred to as a maneuvering instruction as itguides the user how to maneuver (e.g., make a turn) at a junction orjuncture of roads on a route.

The navigation application of some embodiments differently presents, indifferent navigation modes, the turn-by-turn navigation instructions andthe turn-by-turn map views of a route. In some embodiments, thedifferent navigation modes include the driving mode and the pedestrianmode. In the driving mode, the navigation application of someembodiments tailors the presentation of the navigation instructions andthe map views for a user who is driving a car to navigate the route. Inthe pedestrian mode, the navigation application of some embodimentstailors the presentation of the navigation instructions and the mapviews for a user who is walking along the route to the destination.

For instance, the navigation application of some embodiments presentsthe map view in three-dimension (3D) when the navigation application isin the driving mode. When in the pedestrian mode, the navigationapplication provides the map views in two-dimension (2D). Moreover, thenavigation application of some embodiments presents the map views withhigher detailed constructs (e.g., trees, foliage, sidewalks, medians,lanes of roads, road asphalt, cross walks, etc.) that provide a morerealistic and richer 3D view when the navigation application is in thedriving mode. The navigation application shows lower detailed constructsthat provide a simpler 2D view when the navigation application is in thepedestrian mode.

Several detailed embodiments are described in the sections below.Section I describes the navigation application of some embodiments inthe pedestrian mode that allows the user to peek ahead and behind thenavigation instructions of a walking route. Next, Section II describesthe navigation application of some embodiments in the driving mode thatallows the user to peek ahead and behind the navigation instructions ofa driving route. Section III follows with a description of examplesoftware architecture of the navigation application of some embodiments.Section IV describes architecture of a mobile computing device of someembodiments and an electronic system that implements some embodiments ofthe invention. Finally, Section V describes a map service operatingenvironment according to some embodiments.

I. Peeking Ahead and Behind in the Pedestrian Mode

A. Peeking Ahead

FIG. 1 illustrates an example of the navigation application that allowsa user to peek ahead the next navigation instructions for a route beingnavigated by the user. Specifically, this figure illustrates in terms offour stages 105-120 that the navigation application displays a locationthat corresponds to the next navigation instruction in response to theuser's swiping on a banner 125 that displays the current navigationinstruction. This figure illustrates a screen of a device 100 thatdisplays user interface (UI) pages of the navigation application,including a display area of the navigation application. The device 100is a device on which the navigation application executes.

In some embodiments, each of the navigation instructions for the routecorresponds to a location and instructs the user how to maneuver (e.g.,make a left turn) at the location in order to guide the user to followalong the route. When a user travels a route using the navigationapplication, the navigation application displays a current navigationinstruction and a map view that shows a region of a map in which thecurrent position of the user is located (i.e., the current position ofthe device that the user navigating the route).

Different embodiments use different techniques to identify the currentposition of the device. For instance, in some embodiments, thenavigation application uses GPS coordinates received through thedevice's GPS receiver. The navigation application may also receive thecurrent position information from a remote server (not shown) thatemploys Wi-Fi Positioning System (WPS).

In some embodiments, the navigation application displays a navigationinstruction in a banner that resembles a road sign. The navigationapplication in some embodiments places the banner on the top portion ofthe displayed map view. The navigation application allows the user toslide out the banner and slide in another banner that displays the nextnavigation instruction. As the banner displaying the current navigationinstruction slides out and the other banner displaying the nextnavigation instruction slides in, the navigation application of someembodiments changes the zoom level, pans the map view, and/or rotatesthe map view. The navigation application of some embodiments performsthe zooming, panning and/or rotating in such a way that the navigationapplication displays both the current position of the device (i.e., thecurrent position of the user) and the location that corresponds to thenext navigation instruction in the screen of the device together.

At the first stage 105, the navigation application displays a top-downview of a map that shows a route being traveled by the user. Thenavigation application changes the view by showing different areas alongthe route as the user makes progress to the destination of the route. Insome embodiments, the navigation application displays a current positionindicator (e.g., a puck 135) in the map view to indicate the currentposition of the user in the region of the map being displayed. In someembodiments, the navigation application keeps the current positionindicator at a position that is just below the center of the screen.That is, the current position indicator 135 is stationary with respectto the sides of the screen even if the displayed map view changes as theuser moves on the route.

At the first stage 105, the direction of travel by the user is pointingthe top side of the screen because the navigation application of someembodiments updates the map view such that the current direction of thetravel by the user is vertically pointing up in the map view as the usermoves on the route. However, when the user is peeking ahead to see thelocation for the next navigation instruction, the navigation applicationof some embodiments rotates the map view so that the direction (i.e., avector) from the current position of the user to the location for thenext navigation instruction points to the top side of the screen. Thelocation for the next navigation instruction is the end of the nextsection of the route, which starts at the location for the currentnavigation instruction.

At the first stage 105, the navigation application displays the banner125. In some embodiments, a banner displaying a navigation instructionalso displays other information in addition to the navigationinstruction. For instance, the banner 125 displays the remainingdistance to the location for the current navigation instruction and alsoa directional indicator 145 as shown at the first stage 105. Thenavigation application in some embodiments also displays a list control140, which when selected displays the navigation instructions for theroute in a list format.

The route being traveled is partially shown in the map view. In someembodiments, the navigation application differently renders the portionof the route that has not been navigated and the portion of the routethat has been navigated in order to visually distinguish these portions.For instance, as shown at the first stage 105, the portion of the routethat has not been navigated is rendered in black and the portion of theroute that has been navigated is rendered in grey.

The second stage 110 shows that the user starts moving the banner 125 tothe left side of the screen (i.e., to the left side of the display areadisplayed on the screen). In some embodiments, the navigationapplication allows the user to move a banner by dragging the banner tothe direction to which the user wishes to move the banner. At the secondstage 110, the user places the finger on the banner 125 and starts tomove the finger to the left side of the screen while maintaining thetouch with the screen to drag the banner to the left. (The user does nothave to place the finger on the screen when the screen is a near-touchsensitive screen and as long as the device senses as a “touch”).

The third stage 115 shows that the user's finger has dragged the banner125 to the left and another banner 130 that displays the next navigationinstruction has slid in from the right side of the screen by chasing thebanner 125. The navigation application allows the user to drag a bannerpartially out of the screen. In some embodiments, the amount of therotation of the map view the navigation application makes isproportional to the size of the portion of the banner that has slid out.For instance, when it takes a 90-degree clockwise rotation of the mapview to make the direction from the current position of the user to thelocation of the next navigation instruction point to the top side of thescreen, the navigation application rotates the map view by 30 degreesclockwise when a third of the banner slides out of the screen to theleft. As the banner 125 is not completely slid out of the screen at thisstage 110, the navigation application has not fully rotated the map viewto have the direction to point to the top side of the screen.

Moreover, the amount of zooming that the navigation application of someembodiments performs is also proportional to the size of the portion ofthe banner that has slid out of the screen. For instance, when it takesto zoom out the map view by 50 percent to display both the currentlocation and the location for the next navigation instruction, thenavigation application zooms out the map view by 25 percent when a halfof the banner slides out of the screen. At the third stage 115, becausethe banner 125 is not completely slid out of the screen, the navigationapplication has not fully zoomed out the map view display both thecurrent position of the user and the location for the next navigationinstruction.

The navigation application may also pan the map view as the map view isrotated or zoomed out, in order to display on the screen a new region ofthe map that includes both the current position of the device and thelocation for the next navigation instruction. In some embodiments, thenavigation application keeps the current position indicator stationarywith respect to the sides of the screen while the map view is beingzoomed out, rotated and/or panned.

In some embodiments, the map view shows a region of a map from aviewpoint of a virtual camera that is positioned perpendicularly to theground (the map) and has a point of focus in the middle of the region ofthe map being displayed. In these embodiments, the navigationapplication performs zooming in and out by changing the camera'sdistance from the ground. The navigation performs rotating by rotatingthe camera about the point of focus. The navigation performs panning bymoving the point of focus to another location of the map. In theseembodiments, the navigation application translates the movement of thebanner being slid into the movement of the camera.

As shown at the third stage 115, the navigation application of someembodiments does not rotate the puck 135 as the navigation applicationrotates the map view. That is, the person displayed in the puck 135keeps its uprightness with respect to the bottom side of the screen. Inother embodiments, however, the navigation application keeps theuprightness of the puck with respect to the direction of the travel.Therefore, the puck would rotate as the roads rotate.

The fourth stage 120 shows that the user has completely dragged thebanner 125 out of the screen and the banner 130 displaying the nextnavigation instruction is fully displayed in the screen. As shown, thenavigation application has fully zoomed out to a zoom level at which themap view display both the current position of the user and the locationfor the next navigation instruction. The location for the nextnavigation instruction in this example is the junction of the A Streetand the Fair Street at which the user is to turn right according to thenext navigation instruction displayed in the banner 130. The navigationapplication has also rotated the map view such that the direction fromthe current position of the user to the location for the next navigationinstruction points to the top side of the screen. The puck 135 is at thesame position with respect to the sides of the screen.

In the example illustrated in FIG. 1, the user has peeked ahead to viewthe location for the next navigation instruction only. However, thenavigation application of some embodiments allows the user to peek aheadto view as many navigation instructions as possible up to the lastnavigation instruction of the route being traveled. In such cases, thenavigation application performs zooming, rotating and panning to displaythe current location and all the locations for all the future navigationinstructions in the screen together.

For instance, when the user slides out a banner displaying the currentnavigation instruction and then slides out another banner displaying thefirst next navigation instruction, the navigation application of someembodiments slides in a third banner that displays the second nextnavigation instruction in the sequence of navigation instructions forthe route. When the banner displaying the current navigation instructionslides out, the navigation application rotates the map view to have thevector from the current position of the user to the location for thefirst next navigation instruction to point to the top side of thescreen. The navigation application then further rotates the map view tohave the vector from the current position of the user to the locationfor the second next navigation instruction to point to the top side ofthe screen.

Likewise, the navigation application zooms out to display both thecurrent position of the user and the location for the first nextnavigation instruction. The navigation application then zooms out themap view even further to display the current position of the user, thelocation for the first next navigation instruction, and the location forthe second next navigation instruction together in the screen. Thenavigation application also pans the map view as necessary to displaythe current position of the user and the locations for the first andsecond navigation instruction together.

In some embodiments, the navigation application treats the currentposition of the user and the locations for the future navigationinstructions as a group of points of interests (POIs) to be displayedtogether on the map. The navigation application of these embodimentszooms, rotates and/or pans the map view to display this group of POIswithin the screen of the device by moving the virtual camera. Displayinga group of POIs by moving the virtual camera is described further inU.S. patent application Ser. No. 13/632,040, entitled “Virtual Camerafor 3D Maps,” filed Sep. 30, 2012. U.S. patent application Ser. No.13/632,040 is incorporated herein by reference.

The way the map view is displayed at the first stage 105 (e.g., thecurrent direction of the travel pointing up to the top side of thescreen, the current position indicator being maintained at a positionbelow the center of the screen, etc.) is referred to as “navigationview” above and below. The way the map view is displayed at the fourthstage 120 (e.g., the vector from the current location of the user to thelocation for the displayed navigation instruction pointing the top sideof the screen, the current position indicator and the locations for thefuture navigation instructions being displayed in the screen together,etc.) is referred to as “peek view.” The way the map view is displayedat the third stage 115 (e.g., zooming, panning), and/or rotating, arenot fully completed to be the peek view) is referred to as a “partial”peek view.

B. Bouncing Back to Navigation View

FIG. 2 illustrates that the navigation application of some embodimentsbounces a banner back to its original position when the touch on thebanner that dragged the banner out of the screen of a device is notmaintained with the screen. This figure illustrates the bouncing backoperation of the navigation application in terms of five stages 205-225.

At the first stage 205, the navigation application displays a banner 230that displays the current navigation instruction of a route beingtraveled by a user. The user starts dragging the banner 230 to the leftside of the screen.

The second stage 210 shows that the user has dragged the banner 230about a half way out of the screen to the left. As a result, anotherbanner 235 showing the next navigation instruction of the route has slidin a half way into the screen from the right side of the screen. Thenavigation has zoomed out and rotated the map view clockwise. However,because the banner 230 displaying the current navigation instruction hasnot been completely slid out of the screen, the navigation applicationdisplays a partial peek view. That is, the direction of an invisiblevector from the current position of the user to the location for thenext navigation instruction is not yet pointing to the top side of thescreen. The zooming level has not reached the level at which both thecurrent position of the user and the location for the next navigationinstruction are displayed together in the screen.

The third stage 215 shows that the user is no longer touching (or nolonger sensed as a touch by the device) the screen. The user may havelifted up the finger or have slid the finger off the screen aftercompletely dragging the banner 230 out of the screen. The banner 235displaying the next navigation instruction is fully displayed in thescreen. The navigation application thus displays the full peek view forthe next navigation instruction. That is, the navigation application haszoomed out, panned and/or rotated the map view such that the currentposition of the user and the location for the next navigationinstruction are displayed in the screen together. The vector (not shown)from the puck 135 to the location for the next navigation instruction(i.e., the junction of the A street and the Fair Street in this example)also points substantially to the top side of the screen.

In some embodiments, the navigation application maintains the peek viewor the partial peek view only if the touch (or the near-touch) thatdrags the current navigation instruction is maintained. When the touchis not maintained, e.g., due to the user's lifting up the finger thathas been touching the screen or due to sliding the finger out of thescreen, the navigation application restores the navigation view for thecurrent navigation instruction. That is, the navigation applicationslides the banner for the current navigation instruction fully back tothe screen. And the navigation application rotates back, zooms in,and/or pans the map view back such that the current direction of thetravel points to the top side of the screen. In some embodiments,touching the screen and moving the figure while maintaining the touchwith the screen is referred to as a touch drag or a touch dragoperation. The touch drag operation ends when the finger is lifted fromthe screen or falls out of the screen.

The fourth stage 220 shows the partial peek view for the currentnavigation instruction because the navigation application of someembodiments does not discretely restore the navigation view for thecurrent navigation instruction. Rather, the navigation applicationsmoothly transitions from the peek view for the next navigationinstruction to the navigation view. That is, the navigation applicationof some embodiments animates the map view to show the intermediatepartial peek views until the navigation view is fully restored just likethe navigation application does to transition from the navigation viewto the peek view. The fifth stage 225 shows that the navigationinstruction has fully restored the navigation view for the currentnavigation instruction. Thus, the fifth stage 225 in this example looksidentical to the first stage 205.

C. Peeking Behind

FIG. 3 illustrates that the navigation application of some embodimentsallows a user to peek behind the previous navigation instructions for aroute being traveled by the user. This figure illustrates in threestages 305-315 that the navigation application displays a location thatcorresponds to the previous navigation instruction in response to theuser's swiping a banner 320 that displays the current navigationinstruction.

In some embodiments, the navigation application allows the user to slideout the banner in one direction (e.g., to the left) so that anotherbanner that displays the next navigation instruction can slide in. Thenavigation application allows the user to slide out the banner inanother direction (e.g., to the right) so that another banner thandisplays the previous navigation instruction can slide in.

As the banner displaying the current navigation instruction slides outand another banner displaying the previous navigation instruction slidesin, the navigation application of some embodiments changes the zoomlevel, pans the map view, and/or rotates the map view. The navigationapplication of some embodiments performs the zooming, panning androtating in such a way that the navigation application displays both thecurrent position of the device and the location that corresponds to theprevious navigation instruction in the screen of the device together. Insome such embodiments, the navigation application displays the entireprevious section of the route, which ends at the location for theprevious navigation instruction and begins at the location for thenavigation instruction that is prior to the previous navigationinstruction in the sequence of navigation instructions for the route.

At the first stage 305, the navigation application displays thenavigation view for the current navigation instruction. The navigationapplication displays the banner 320 that displays the current navigationinstruction. The navigation application also displays the puck 135 thatindicates the current position of the user who carries the device. Atthis stage 305, the user starts swiping the banner 320 to the right sideof the screen using a finger.

The second stage 310 shows that the user's finger has dragged the banner320 to the right and another banner 325 that displays the previousnavigation instruction has slid in from the left side of the screen. Asthe banner 320 that displays the current navigation instruction has notcompletely slid out of the screen at this stage 310, the navigationapplication displays a partial peek view.

For displaying a full peek view for a previous navigation instruction,the navigation application rotates the map view to make a vector fromthe location for the previous navigation to the current position of theuser point to the top side of the screen. In the example of this figure,this vector (not shown) is from the junction of the B Street and theFoothill Street to the puck 135. However, in other embodiments, thenavigation application makes a vector, from the beginning of theprevious section of the travel, rather than from the end of the previoussection of the travel, to the current position of the user, point to thetop side of the screen. In the example of this figure, this vector isfrom the junction of the B Street and the C Street to the puck 135 asshown at the third stage 315 because the previous section of the routebegins at this junction.

To show the full peek view, the navigation application of someembodiments also pans the map view to move the puck 135 to a positionabove the center of the screen as shown at the fourth stage 315. In thismanner, the navigation application visually distinguishes a peek viewfor a past navigation instruction from a peek view for a futurenavigation instruction.

At the second stage 310, the navigation application has not fullyrotated the map to reach the full peek view displayed at the third stage315. Also, the navigation application has not panned the map view enoughto move the puck 135 above the center of the screen. The navigationapplication has not zoomed out to fully display the previous section ofthe route.

The third stage 315 shows that the user has completely dragged thebanner 320 out of the screen and the banner 325 for the previousnavigation instruction is fully displayed in the screen. The navigationapplication now displays the full peek view for the previous navigationinstruction.

As shown, the navigation application has fully zoomed out to a zoomlevel at which the map view display both the current position of theuser and the entire previous section of the route. The section of theroute for the previous navigation instruction in this example is theportion of the B Street between the junction of the Foothill Street andthe junction of the B Street and the C Street. The navigationapplication has also rotated the map view such that the direction fromthe beginning of the previous section of the route to the currentposition of the user points to the top side of the screen. The puck 135has moved up to a position above the center of the screen.

In the example illustrated in FIG. 3, the user has peeked behind to viewthe location for the previous navigation instruction and the previoussection of the route only. However, the navigation application of someembodiments allows the user to peek behind to view as many pastnavigation instructions and sections of the route as possible all theway back to the first navigation instruction of the route. In suchcases, the navigation application performs zooming, rotating and panningto display the current location and all the locations for all theprevious navigation instructions in the screen together.

In some embodiments, the navigation application uses one direction ofrotation (e.g., clockwise) for reaching a peek view for a futurenavigation instruction and another direction of rotation for reaching apeek view for a past navigation instruction. Alternatively orconjunctively, the navigation application uses either direction ofrotation that gives the least amount of rotation to reach a peek view.That is, for example, rather than rotating the map by 270 degreesclockwise, the navigation application of these embodiments rotates themap 90 degrees counterclockwise to reach a peek view.

D. Responding to Touch Movement

FIG. 4 illustrates an example of the navigation application of someembodiments that follows the movement of the touch on the screen inorder to change the map view smoothly as the touch on the screen moves.This figure shows in four stages 405-420 that the navigation applicationdisplays partial peek views as the touch on the screen moves away fromthe initial position of the touch.

At the first stage 405, the user touches a banner 425 that displays thecurrent navigation instruction of a route being traveled by the user.The user starts dragging the banner 425 to the right side of the screenby moving the finger to the right side while maintaining the touch withthe screen.

In some embodiments, the navigation application moves a bannerhorizontally by chasing the horizontal movement of the touch. Themovement of the touch does not have to be perfectly parallel to ahorizontal line of the screen in some embodiments. When the touch's pathon the screen is not parallel to the top or bottom side of the screen,the navigation application takes a horizontal component of an invisiblevector drawn from the touch's initial position to the current positionon the screen and moves the banner by a length that is proportional tothe length of the horizontal component. Moreover, the navigationapplication of some embodiments moves the banner to chase the movementof the touch even if the touch falls out of the banner (but the touch isstill on the screen).

At the second stage 410, the user has dragged the banner 425 to theright and the right half of the banner 425 has slid out of the screen.The navigation application has slid in a banner 430 for the previousnavigation instruction because the user has dragged the banner 435 tothe right side of the screen. The navigation application displays apartial peek view for the previous navigation instruction as shown. Atthe stage 410, the user maintains the touch by, e.g., not lifting up thefinger from the screen. The user also starts dragging the banner 425 tothe left by moving the finger to the left while maintaining the touchwith the screen.

At the third stage 415, the user has moved the finger near the initialposition on the screen at which the finger was at the first stage 405.The navigation application displays the navigation view for the currentnavigation instruction. The user also drags the banner 425 to the leftside of the screen by keeping moving the finger to the left whilemaintaining the touch with the screen.

At the fourth stage 420, the user has dragged the banner 425 and theleft half of the banner 425 has slid out of the screen. The navigationapplication has slid in a banner 435 for the next navigation instructionbecause the user has dragged the banner 435 to the left side of thescreen. The navigation application displays a partial peek view for thenext navigation instruction as shown. At the stage 420, the usermaintains the touch with the screen.

FIG. 5 conceptually illustrates a process 500 that the navigationapplication of some embodiment performs to present the navigation viewfor the current navigation instruction of a route and a peek view forthe previous or next navigation instruction of the route. The navigationapplication of some embodiments performs the process 500 on a devicethat has a touch-sensitive screen and/or a near-touch sensitive screenthat displays the output of the navigation application. The process 500starts when the navigation application is presenting a map view for theroute being traveled by a user for the current position of the user.

The process 500 begins by determining (at 505) whether the user istouching the screen of the device. In some embodiments, the process 500determines whether the user is touching the screen based on theinformation (e.g., information whether the screen is being touched,coordinates of the touch if the user is touching the screen at one ormore locations of the screen, etc.) from a touch interface of thedevice. When the process 500 determines (at 505) that the user is nottouching the screen, the process 500 proceeds to 565, which is describedfurther below.

When the process 500 determines (at 505) that the user is touching thescreen, the process 500 identifies (at 510) the location of the touch anthe screen. In some embodiments, the process 500 identifies the locationof the touch on the screen from the information received from the touchinterface of the device.

Next, the process 500 of some embodiments optionally determines (at 515)whether the touch is on a banner that is currently displayed in thescreen. The banner displays a navigation instruction for the route thatguides the user at a location on the route in order for the user toreach the destination of the route. The banner is occupying a portion ofthe screen and is overlaid on the map view in some embodiments. Theprocess 500 of some embodiments determines that the touch is on thebanner when the coordinates of the screen fall within a set ofcoordinates of the screen that the banner is currently occupying. Insome embodiments, the screen has a coordinate system. The coordinates ofthe touch and the banner are of this coordinate system.

When the process 500 determines (at 515) that the touch is not on thebanner, the process 500 loops back to 505 to check whether the touch ismaintained with the screen. When the process 500 determines (at 515)that the touch is on the banner, the process 500 determines (at 520)whether the touch has moved on the screen. In some embodiments, theprocess 500 keeps track of the locations of the touch while the touch ismaintained with the screen. The process 500 determines that the touch ismoving on the screen when the location of the touch is changing whilethe touch is maintained.

When the process 500 determines (at 520) that the touch has not moved onthe screen, the process 500 loops back to 505 to check whether the touchis maintained with the screen. When the process 500 determines (at 520)that the touch has moved on the screen, the process 500 identifies (at525) the length and the direction of the movement that the touch hasmade. In some embodiments, the process 500 identifies a vector on thecoordinate system of the screen that represents the movement of thetouch and identifies only the horizontal component (e.g., anx-component) of the vector as the length of the movement. In some suchembodiments, the process 500 identifies the length of the horizontalcomponent of the vector as zero when the vector is not substantiallyparallel to a horizontal line on the screen's coordinate system (e.g.,not within 40 degrees with respect to a horizontal line of the screen).That is, the process 500 ignores the movement of touch if the movementis not considered a horizontal swipe on the screen.

The process 500 then determines (at 530) whether the movement of thetouch is in a first direction (e.g., to the left side of the screen). Asmentioned above, the process 500 of some embodiments considers only thehorizontal component of the vector that represents the movement. Theprocess 500 of these embodiments determines whether the movement of thetouch is in the first direction based on the direction of the horizontalcomponent of the vector.

When the process 500 determines (at 530) that the movement of the touchis not in the first direction, the process 500 proceeds to 540, which isdescribed further below. When the process 500 determines (at 530) thatthe movement of the touch is in the first direction, the process at 535slides out the banner and slides in another banner that displays thenext navigation instruction of the route. The process 500 slides out thebanner by a length that is proportional to the length of the movement ofthe touch. As the process 500 slide out the banner, the process 500 alsomodifies (at 545) the map view to display a peek view for peeking aheadthe next navigation instruction.

The process in some embodiments modifies the map view by rotating,zooming and/or panning the map view such that (1) a vector, from thecurrent location of the user to the location of the next navigationinstruction (i.e., the end of the section of the route for the nextnavigation instruction), points to the top side of the screen and (2)both the current position of the user and the location for the nextnavigation instruction are displayed in the screen together. The processthen proceeds to 560, which is described further below.

When the process 500 determines (at 530) that the movement of the touchis not in the first direction, the process 500 determines (at 540)whether the movement of the touch is in the second direction. In someembodiments, the first and second directions are the opposite directionsto each other. When the process 500 determines (at 540) that themovement of the touch is not in the second direction, the movement ofthe touch is neither in the first direction nor in the second direction.That is, the movement is deemed to have a zero length or is notconsidered as a horizontal movement. In such cases, the process 500loops back to 505 to check whether the touch is maintained with thescreen.

When the process 500 determines (at 540) that the movement of the touchis in the second direction, the process at 550 slides out the banner andslides in another banner that displays the previous navigationinstruction of the route. The process 500 slides out the banner by alength that is proportional to the length of the movement of the touch.As the process 500 slide out the banner, the process 500 also modifies(at 555) the map view to display a peek view for peeking behind.

The process in some embodiments modifies the map view by rotating,zooming and/or panning the map view such that (1) a vector, from thebeginning of the section of the route for the previous navigationinstruction to the current location of the user, points to the top sideof the screen and (2) both the current position of the user and thebeginning of the section for the previous navigation instruction aredisplayed in the screen together. The process in other embodimentsmodifies the map view by rotating, zooming and/or panning the map viewsuch that (1) a vector, from the location for the previous navigationinstruction to the current location of the user, points to the top sideof the screen and (2) both the current position of the user and thelocation for the previous navigation instruction are displayed in thescreen together.

The process then determines (at 560) whether the banner displaying thecurrent navigation instruction has been slid out of the screen. When theprocess determines (at 560) that the banner has not been slid out of thescreen, the process loops back to 505 to check whether the touch ismaintained with the screen. Otherwise the process ends.

When the process 500 determines (at 505) that the user is not touchingthe screen, the process 500 of some embodiments determines (at 565)whether a peek view is being displayed in the screen. That is, theprocess 500 determines whether the process has rotated, zoomed out,and/or panned the map view for the next or previous navigationinstruction. When the process determines (at 565) that the peek view isbeing displayed, the process bounces (at 570) back to the navigationview from the current navigation instruction. This is because the touchis no longer maintained and the process of some embodiments bounces backto the navigation view from the peek view when the touch is notmaintained. When the process 500 determines (at 565) that the peek viewis not being displayed, the process 500 loops back to 505 to checkwhether the user touches the screen.

E. Automatically Reverting to Navigation View

FIG. 6 illustrates in five stages 605-625 that the navigationapplication backs out from a peek view for the next navigationinstruction of a route to a navigation view for the current navigationinstruction of the route when the user moves close to or arrives at alocation for the current navigation instruction.

The first and second stages 605 and 610 are similar to the first andsecond stages 205 and 210 described above by reference to FIG. 2. Thatis, at the first and second stages 605 and 610, the user has dragged abanner 630 that displays the current navigation instruction for thecurrent location of the user to the left side of the screen. At thesecond stage 610, the navigation application displays a partial peekview for the next navigation instruction.

At the third stage 615, like at the third stage 215 of FIG. 2, thenavigation instruction displays the full peek view for the nextnavigation instruction. However, in contrast to the navigationapplication of some embodiments at the third stage 215 of FIG. 2, thenavigation application of some embodiments at the third stage 615 doesnot start restoring the navigation view for the current navigationinstruction even if the touch is not maintained. The navigationapplication of these embodiments keeps the peek view for the nextinstruction even if the touch is not maintained with the screen.Moreover, the navigation application of some of these embodimentsupdates the position of the current position indicator (e.g., a puck645) in the peek view. As shown at the third stage 615 by the positionof the puck 645 on the map, the user has moved to a position that iswithin a block from the location for the left turn to the A Street. Theuser had been more than a block away from the location for the left turnto the A Street as shown by the previous stage 610.

The fourth stage 620 shows that the navigation application stilldisplays the peek view for the next navigation instruction. The user hasmoved closer to the location for the left turn as indicated by theposition of the puck 645 in the map. In some embodiments, the navigationinstruction notifies the user of an imminent turn when the position ofthe user falls within a threshold distance (e.g., five feet) from thelocation for the turn. For instance, the navigation application of someembodiments at the fourth stage 620 presents a short audiblenotification (e.g., a short audible sound such as “ding”) to the user tonotify the user of the imminent turn.

When the user reaches the location for the turn, the navigationapplication of some embodiments automatically reverts back to thenavigation view for the turn. As shown at the fifth stage 625, thenavigation application restores the navigation view for the currentnavigation instruction as the user arrives at the location for the leftturn to the A Street. The navigation application of some embodimentsalso updates the content displayed on the banner 630 for the currentnavigation instruction. For instance, as shown, the navigationapplication does not display the remaining distance to the location ofthe turn because the user has reached the location for the turn.

FIG. 7 illustrates another situation in which the navigation applicationof some embodiments automatically reverts to the navigation view for thecurrent navigation instruction from the peek view for the nextnavigation instruction. Specifically, this figure illustrates in termsof five stages 705-725 that the navigation application backs out fromdisplaying the peek view and automatically reverts to the navigationview when a defined period of time elapses. This figures alsoconceptually illustrates a clock after each of the first four stages705-720 to indicate the time at which the stage ends.

At the first stage 705, the navigation application displays a banner 730that displays the current navigation instruction of a route beingtraveled by a user. The user starts dragging the banner 730 to the leftside of the screen. The navigation application advances to the nextstage 710 at 12:15 PM as indicated by the clock depicted between thestages 705 and 710.

At the second stage 710, the navigation application displays a partialpeek view for the next navigation instruction as the user drags thebanner 730 about a half way out of the screen to the left. Thenavigation application advances to the next stage 715 at 12:15 PM asindicated by the clock depicted between the stages 710 and 715.

At the third stage 715, the navigation instruction displays the fullpeek view for the next navigation instruction. A banner 735 displayingthe next navigation instruction is fully displayed. The user has movedto a position that is within a block from the location for the left turnto the A Street as indicated by a current position indicator 740. Theuser had been more than a block away from the location for the left turnto the A Street as shown by the previous stage 710. The navigationapplication advances to the next stage 720 at around 12:25 PM asindicated by the clock depicted between the stages 715 and 720.

The fourth stage 720 shows that the navigation application stilldisplays the peek view for the next navigation instruction. The user hasnot moved from the position at which the user was at the previous stage715. The user stops moving and maintains the position as indicated bythe current position indicator 740. The navigation application advancesto the next stage 725 at around 12:29 PM as indicated by the clockdepicted between the stages 720 and 725.

As mentioned above, the navigation application of some embodimentsreverts to the navigation view for the current navigation instructionfrom the peek view for the future or past navigation instructions when adefined period of time elapses while the navigation application isdisplaying the peek view. This period of time is predefined for thenavigation application or the navigation application allows the user todetermine the period of time. In some embodiments, the period of time isset to a certain period of time (e.g., three minutes) when thenavigation application is in the pedestrian mode. The fifth stage 725shows that the navigation application of some embodiments has revertedto the navigation view for the current navigation instruction becausemore than the defined period of time is lapsed (e.g., from 12:25PM to12:29PM) while the navigation application displays the peek view.

FIG. 8 conceptually illustrates a process 800 that the navigationapplication of some embodiment performs to revert automatically to thenavigation view for the current navigation instruction of a route beingtraveled by a user. The navigation application of some embodimentsperforms the process 800 on a device that has a touch-sensitive screenand/or a near-touch sensitive screen that displays the output of thenavigation application. The process 800 starts when the navigationapplication is displaying a map view for the route.

The process 800 begins by displaying (at 805) a navigation view for thecurrent navigation instruction. That is, the process 800 displays (at805) the map view such that the current direction of the travel by theuser is pointing to the top side of the screen and the map view isupdated as the user makes progress on the route.

Next, the process 800 determines (at 810) whether the process 800 shoulddisplay a peek view for peeking ahead or behind. In some embodiments,the process 800 determines that the peek view is to be displayed whenthe process 800 receives, while displaying the navigation view, a touchmovement that causes the navigation application to slide out a bannerdisplaying the current navigation instruction.

When the process 800 determines (at 810) that the process 800 is not todisplay the peek view, the process 800 loops back to 805 to display thenavigation view. When the process determines (at 810) that the process800 should display the peek view, the process 800 (at 815) displays thepeek view and identifies the start time of the peek view display. Insome embodiments, the process 800 obtains the time information for aninstance in time at which the process 800 starts modifying the map viewto display the peek view. The process 800 records the time as the starttime of the peek view display.

Next, the process 800 determines (at 820) whether the process hasreceived a touch movement that requires an update of the map view. Theprocess 800 determines that the received touch movement requires anupdate of the peek view when the movement causes the navigationapplication to move a banner being displayed in the screen.

When the process 800 determines (at 820) that the process has notreceived a touch movement or the received touch movement does notrequire an update of the map view, the process 800 proceeds to 835,which is described further below. When the process 800 determines thatthe received touch movement requires an update of the map view, theprocess 800 updates the map view (at 825) based on the touch movement.For instance, the process 800 further rotates, pans and or zooms in orout the map view.

The process 800 then determines (at 830) whether the map view has turnedinto the navigation view for the current navigation instruction as aresult of updating the map view. That is, in some cases, the user maydrag in the banner that displays the current navigation instruction backinto the screen as they peek ahead and/or behind. In such cases, it isthe navigation view rather than the peek views that the navigation endsup displaying.

When the process determines (at 830) that the map view has turned intothe navigation view, the process 800 loops back to 805 to display themap view. When the process determines (at 830) that the map view has notturned into the navigation view, the process 800 proceeds to 835 toidentify the current position of the user and to move the currentposition indicator in the map view if necessary.

Next, the process 800 determines (at 840) whether a defined period oftime has elapsed since the identified (at 815) start time for the peekview display. The period of time is for determining whether thenavigation application has been displaying the peek view for too long.In some embodiments, this period of time is preconfigured for thenavigation application. Alternatively or conjunctively, the user can setthis period of time for the navigation application in some embodiments.

When the process 800 determines (at 840) that the period of time haselapsed since the start of the peek view display, the process 800reverts (at 860) back to the navigation view. When the process 800determines (at 840) that the period of time has not elapsed since thestart of the peek view display, the process 800 determines (at 845)whether the current position of the user is within a threshold distance(e.g., five feet, 200 feet, 1 mile, depending on the speed of the userand whether the navigation application is in the driving mode or in thepedestrian mode) from the location for the current navigationinstruction. This threshold distance is for determining whether the userhas come close to the location for the current navigation instruction.

When the process 800 determines (at 845) that the current position ofthe user is not within the threshold distance from the location for thenext navigation instruction, the process 800 loops back to 820 to checkwhether the process has received a touch movement that requires anupdate of the map view. When the process 800 determines (at 845) thatthe current position of the user is within the threshold distance, theprocess 800 determines (at 850) whether the current position of the useris at the location for the current navigation instruction.

When the process 800 determines (at 850) that the current position ofthe user is not at the location for the current navigation instruction,the process 800 presents (at 855) an audible notification to the user(if the process has not given the audible notification to the useralready). This is because, at this point, the current position of theuser is within the threshold distance from the location for the currentnavigation instruction but is not at the location. The process 800 thenloops back to 820 to check whether the process has received a touchmovement that requires an update of the map view.

When the process 800 determines (at 850) that the current position ofthe user is at the location for the current navigation instruction, theprocess 800 reverts (at 860) to the navigation view from the peek view.The process 800 then ends.

Having described peeking ahead and behind for the navigation applicationthat is in the pedestrian mode, the next Section II now describespeeking ahead and behind for the navigation application that is in thedriving mode.

II. Peeking Ahead and Behind in the Driving Mode

A. Peeking Ahead

In some embodiments, the navigation application allows a user to peekahead or behind the navigation instructions while the navigationapplication is in the driving mode in order to present the navigationinstructions and the map views suitable for the user who is driving.FIG. 9 illustrates an example of the navigation application that allowsa user to peek ahead the next navigation instructions for a route thatis being presented in the driving mode. Specifically, this figureillustrates in terms of four stages 905-920 that the navigationapplication displays a location that corresponds to the next navigationinstruction in response to the user's swiping up the screen of a deviceon which the navigation application executes.

At the first stage 905, the navigation application of some embodimentsis in the driving mode, displaying the map view for the currentnavigation instruction in 3D. In some embodiments, the 3D map view showsan area of a map from a viewpoint of a virtual camera that chases thecar by flying behind the car. Details of the movement of the virtualcamera movement to generate 3D map views are further described in theabove-incorporated U.S. patent application Ser. No. 13/632,040.

As shown at the stage 905, the constructs (e.g., buildings and roads,etc.) in the map are rendered in 3D and a puck 935 that indicates thecurrent position of the user is also rendered in 3D. The navigationapplication is also displaying a navigation view for the currentnavigation instruction. The current direction of travel points to thetop side of the screen and the puck 935 is placed at a position belowthe center of the screen.

The navigation application displays a banner 925 that displays thecurrent navigation instruction for a route. The navigation applicationof some embodiments also displays several floating controls, including a3D control 940 and the list control 140 (described above by reference toFIG. 1). The 3D control 940 is a control for viewing a map in 3D in someembodiments. The navigation application provides the 3D control 750 as aquick mechanism of getting into and out of a 3D view. At the first stage905, the 3D control 750 is rendered in grey to indicate that the mapview is displayed in 3D.

Like in a navigation view in 2D presented by the navigation applicationin the pedestrian mode, when the user is peeking ahead to see thelocation for the next navigation instruction, the navigation applicationrotates the map view such that the direction of a vector from thecurrent position of the user to the location for the next navigationinstruction (i.e., the end of the next section of the route) points tothe top side of the screen.

The second stage 910 shows that the user starts swiping up the screen.In some embodiments, the navigation application in the driving modeallows the user to move a banner by swiping the screen vertically usingone or more fingers. In some embodiments, the navigation slides thebanner to the left when the user swipes up the screen. The navigationapplication of these embodiments slides the banner to the right when theuser swipes down the screen.

In some embodiments, the navigation application recognizes as swipe upsand downs the swipes that are not perfectly vertical with respect to thesides of the screen. For instance, the navigation application recognizesa swipe as a swipe up or a swipe down, when the swipe the user performsis within a certain degrees (e.g., 40 degrees) from a vertical line ofthe screen.

The third stage 915 shows that the navigation has slid out the banner925 to the left and slid in another banner 930 from the right side ofthe screen as the user swipes up the screen. The banner 930 displays thenext navigation instruction. At this stage 915, both of the banner 925and the banner 930 are displayed in the screen partially. This isbecause, in some embodiments, the distance by which a banner moves isproportional to the vertical length of the swipe that the user performs.For instance, when it takes a swipe with a length of a banner to move anentire banner out of the screen, the navigation moves a half of thebanner when the swipe is a half as long as the banner.

Like the navigation view in 2D, the amount of the rotation of the mapview in 3D that the navigation application performs is also proportionalto the size of the portion of the banner that has slid out. Forinstance, when it takes a 90-degree clockwise rotation of the map viewto make the vector from the current position of the user to the locationfor the next navigation instruction point to the top side of the screen,the navigation application rotates the map view by 30 degrees clockwisewhen a third of the banner slides out of the screen to the left. As thebanner 925 is not completely slid out of the screen at this stage 910,the navigation application has not fully rotated the map view to havethat vector to point to the top side of the screen.

Like the navigation view in 2D, the amount of zooming the map view in 3Dthat the navigation application of some embodiments performs is alsoproportional to the size of the portion of the banner that has slid outof the screen. For instance, when it takes to zoom out the map view by50 percent to display both the current location and the location for thenext navigation instruction, the navigation application zooms out themap view by 25 percent when a half of the banner slides out of thescreen. At the third stage 915, because the banner 925 is not completelyslid out of the screen, the navigation application has not fully zoomedout the map view display both the current position of the user and thelocation for the next navigation instruction.

Like navigation application does when rendering the map views in 2D, thenavigation application may also pan the 3D map view as the 3D map viewis rotated or zoomed out, in order to display on the screen a new regionof the map that includes both the current position of the device and thelocation for the next navigation instruction. In some embodiments, thenavigation application keeps the current position indicator stationarywith respect to the sides of the screen while the map view is beingzoomed out, rotated and/or panned.

In some embodiments, the navigation application performs the rotating,zooming and/or panning by moving the virtual camera to a position atwhich (1) the camera can view both the current position of the user andthe location for the next navigation instruction and (2) the camerapoints to the direction of the vector from the current position of theuser to the location for the next navigation instruction. In some cases,the road on which the user is currently on and the puck that indicatesthe current position of the user may be blocked by the constructs (e.g.,buildings) from the viewpoint of the virtual camera. In such cases, thenavigation application of some embodiments may render the constructsblocking the road and the puck translucently such that the road and thepuck are visible from the viewpoint of the virtual camera. Alternativelyor conjunctively, the navigation application renders the constructsblocking the road and the puck flat to the ground so that they do notblock the road or the puck from the viewpoint of the virtual camera.

The navigation application moves the viewpoint of the camera furtheraway from a particular location on the ground of the virtual 3D space inorder to zoom out the map view. To zoom in the map view, the navigationapplication moves the viewpoint closer to the particular location. Thenavigation application moves the viewpoint of the virtual camera whilekeeping the altitude from the ground of the virtual 3D space to pan themap view. The navigation application moves the viewpoint of the camerato follow a perimeter of a circle that has the particular location asthe center of the circle, in order to rotate the map view. More detailsof the movement of the virtual camera to zoom, pan and rotate the mapviews are further described in the above-incorporated U.S. patentapplication Ser. No. 13/632,040.

As shown at the third stage 915, the navigation application of someembodiments changes the appearance of the puck 935 in 3D so that thepointer displayed on top of the puck points to the current direction ofthe travel. At the third stage 915, the user continues performing theswipe up.

The fourth stage 920 shows a 3D peek view for the next navigationinstruction after the user has swiped up for an enough length of thescreen. The navigation application has completely slid the banner 925out of the screen. The navigation application has also slid in thebanner 930 that displays the next navigation instruction such that thebanner 930 is fully displayed in the screen. As shown, the navigationapplication has fully zoomed out to a zoom level at which the map viewdisplay both the current position of the user and the location for thenext navigation instruction. The location for the next navigationinstruction in this example is the junction of the B Street and theState Street at which the user is to turn left according to the nextnavigation instruction displayed in the banner 130. The navigationapplication has also rotated the map view such that the direction fromthe current position of the user to the location for the next navigationinstruction points to the top side of the screen. The puck 935 is at thesame position with respect to the sides of the screen as the positionthe puck 935 was in the previous stages 905-910.

In the example illustrated in FIG. 9, the user has peeked ahead to viewthe location for the next navigation instruction only. However, like inthe case of 2D navigation, the navigation application of someembodiments allows the user to peek ahead to view as many navigationinstructions as possible up to the last navigation instruction of theroute being traveled. In such cases, the navigation application performszooming, rotating and/or panning to display the current location and allthe locations for all the future navigation instructions in the screentogether.

In some embodiments, the navigation application does not render some ofthe constructs in the map view in 3D. For instance, the navigationapplication of some embodiments may render the buildings shown at thestages of FIG. 9 flat. As a result, the map view in these embodimentsdisplays the map view at a perspective angle.

B. Bouncing Back to Navigation View

FIG. 10 illustrates that the navigation application of some embodimentsbounces a banner back to its original position when the touch on thescreen that caused the navigation application to slide the banner out ofthe screen of a device is removed from the screen. This figureillustrates the bouncing back operation of the navigation applicationrunning in the driving mode in terms of five stages 1005-1025.

At the first stage 1005, the navigation application is in the drivingmode, displaying the map view for the current navigation instruction in3D. The navigation application displays a banner 1030 that displays thecurrent navigation instruction of a route being traveled by a user. Theuser starts swiping up the screen by touching the screen with twofingers and starting to move the fingers up towards the top side of thescreen while maintaining the touches.

The second stage 1010 shows that the user has moved up the fingers whilemaintaining the touches with the screen. As the touches move upward tothe top side of the screen, the navigation application has slid thebanner 1030 a half way out of the screen to the left and has slid abanner 1035 showing the next navigation instruction of the route a halfway into the screen from the right side of the screen. The navigationapplication has also zoomed out the map view and rotated the map view.However, because the banner 1030 displaying the current navigationinstruction has not been completely slid out of the screen, thenavigation application displays a partial peek view in 3D. That is, thedirection of the vector from the current position of the user to thelocation for the next navigation instruction is not yet pointing to thetop side of the screen. The navigation application has not yet zoomedout enough to display the current position of the user and the locationfor the next navigation instruction together in the screen. Moreover,the navigation application has not panned the map view enough to displaythe location of the next navigation instruction in the screen.

The third stage 1015 shows that the user has moved up the touches allthe way up to the top edge of the screen and then out of the screen. Inresponse, the navigation application of some embodiments has completelyslid the banner 1030 out of the screen and has fully slid in the banner1035 for the next navigation instruction.

In some embodiments, the navigation application slides out at most onebanner per swipe. That is, even if the length of the swipe exceeds alength that is required to slide out a banner, the navigationapplication does not slide out the banner for the next navigationinstruction for the exceeding length. In other embodiments, thenavigation application slides out more than one banner per swipe whenthe length of the swipe exceeds the length that is required to slide Outone banner. In such cases, the navigation application slides in a bannerfor the navigation instruction that is after the next navigationinstruction.

In some embodiments, the navigation application considers the speed atwhich the touches of the swipe move on the screen. In some of theseembodiments, when the user performs the swipe faster than a certainthreshold speed, the navigation instruction slides out a bannerregardless of the length of the swipe. For instance, the navigation ofsome embodiments slides a banner completely out of the screen and slidesin another banner completely even if the length of the swipe that theuser has performed is shorter than a length that is required to move abanner, as long as the speed of the swipe is faster than the thresholdspeed.

At the third stage 1015, the navigation application displays a 3D peekview for the next navigation instruction. That is, the navigationapplication has zoomed out, panned, and/or rotated the map view suchthat the current position of the user and the location for the nextnavigation instruction are displayed in the screen together. Thedirection of the vector from the current position of the user to thelocation for the next navigation instruction points to the top side ofthe screen. The third stage 1015 also shows that the user is no longermaintaining the touch with the screen. The user may have lifted up orhave slid one or both of the fingers off the screen.

In some embodiments, the navigation application maintains the 3D peekview or the 3D partial peek view only if the touches (or thenear-touches) that caused the navigation application to display the peekview for the next navigation instruction are maintained. When thetouches are not maintained (e.g., due to the user's lifting up orsliding out one or more fingers off the screen), the navigationapplication reverts back to the navigation view for the currentnavigation instruction from the peek view for the next navigationinstruction. That is, the navigation application slides back the bannerthat displays the current navigation instruction fully back to thescreen. The navigation application smoothly rotates back, zooms in, andpans the map view back such that the current direction of the travelpoints back to the top side of the screen and the current positionindicator goes back to the position below the center position of thescreen.

The fourth stage 1020 shows the partial peek view in 3D for the currentnavigation instruction because the navigation application of someembodiments does not discretely revert to the navigation view for thecurrent navigation instruction. Rather, the navigation applicationsmoothly transitions from the peek view for the next navigationinstruction to the navigation view. That is, the navigation instructiondoes not jump back to the navigation view from the peek view withoutdisplaying the intermediate partial peek views. In some embodiments, thenavigation application of some embodiments animates the map view fromthe peek view to the navigation view to show the intermediate partialpeek views until the navigation view is fully restored.

The fifth stage 1025 shows that the navigation instruction has fullyrestored the navigation view for the current navigation instruction.Thus, the fifth stage 1025 in this example looks identical to the firststage 1005.

C. Peeking Behind

FIG. 11 illustrates that the navigation application of some embodimentsallows a user to peek behind the previous instructions for a route thatis being presented in the driving mode. This figure illustrates in threestages 1105-1115 that the navigation application displays a locationthat corresponds to the previous navigation instruction in response tothe user's swiping the screen of the device on which the navigationapplication executes.

The navigation application of some embodiments slides out to onedirection (e.g., to the left side of the screen) a banner that displaysthe current navigation instruction as the user swipes the screen upwardto the top side of the screen. The navigation application slides out thebanner to another direction (e.g., to the right side of the screen) asthe user swipes the screen downward to the bottom side of the screen.

As the banner displaying the current navigation instruction slides outand another banner displaying the previous navigation instruction slidesin, the navigation application of some embodiments zooms, pans and/orrotates the map view. The navigation application of some embodimentsperforms the zooming, panning and/or rotating in such a way that thenavigation application displays both the current position of the deviceand the location that corresponds to the previous navigation instructionin the screen of the device together. In some such embodiments, thenavigation application displays the entire previous section of theroute, which ends at the location for the previous navigationinstruction and begins at the location for the navigation instructionthat is prior to the previous navigation instruction in the sequence ofnavigation instructions for the route. As mentioned above, thenavigation application of some embodiments performs the zooming, panningand/or rotating by changing the viewpoint of the virtual camera bymoving the camera in the virtual 3D space.

At the first stage 1105, the navigation application displays thenavigation view for the current navigation instruction in 3D. Thenavigation application displays a banner 1120 that displays the currentnavigation instruction. The navigation application also displays a puck1130 that indicates the current position of the user who may be drivinga car. At this stage 1105, the user starts swiping down the screen bytouching the screen with two fingers and starting to move the fingersdown to the bottom side of the screen while maintaining the touches.

The second stage 1110 shows that the user has moved down the touchestowards the bottom side of the screen. In response, the navigationapplication has moved the banner 1120 a half way out to the right sideof the screen and slide in another banner 1125 that displays theprevious navigation instruction from the left side of the screen tofollow the banner 1120.

For displaying a full peek view for a previous navigation instruction,the navigation application rotates the map view to make a vector fromthe location for the previous navigation to the current position of theuser point to the top side of the screen. In the example of this figure,this vector (not shown) is from the junction of the C Street and theUnion Street to the puck 1135. However, in other embodiments, thenavigation application makes a vector, from the beginning of theprevious section of the travel, rather than from the end of the previoussection of the travel, to the current position of the user, point to thetop side of the screen. In the example of this figure, this vector isfrom the junction of the C Street and the D Street to the puck 1135 asshown at the third stage 1115 because the previous section of the routebegins at this junction.

To show the full peek view, the navigation application of someembodiments also pans the map view to move the puck 1135 to a positionabove the center of the screen as shown at the fourth stage 1115. Inthis manner, the navigation application visually distinguishes a 3d peekview for a past navigation instruction from a 3D peek view for a futurenavigation instruction.

At the second stage 1110, as the banner 1120 that displays the currentnavigation instruction has not been completely slid out of the screen atthis stage 1110, the navigation application displays a partial peek viewin 3D. That is, the navigation application has not fully rotated thefigure to have the direction of the vector from the beginning of thesection of the route for the previous navigation instruction (e.g., thesection of the route between the location for the previous turn and thelocation for the turn prior to the previous turn) to the currentposition of the user to point to the top side of the screen. At thesecond stage 1115, the navigation. application of some embodiments hasnot zoomed out the map view to display both the current position of theuser and the beginning of the previous section of the route.

The third stage 1115 shows that the user has swiped the screen down andout of the screen. In response, the navigation application hascompletely slid out the banner 1125 and displays the entire banner 1125that displays the previous navigation instruction. The navigationapplication displays the full peek view for the previous navigationinstruction in 3D.

As shown, the navigation application has fully zoomed out to a zoomlevel at which the map view display both the current position of theuser and the entire previous section of the route. The section of theroute for the previous navigation instruction in this example is theportion of the C Street between the junction of the C Street and theUnion Street and the junction of the C Street and the D Street. Thenavigation application has also rotated the map view such that thedirection from the beginning of the previous section of the route to thecurrent position of the user points to the top side of the screen. Thepuck 1135 has moved up to a position above the center of the screen.

In the example illustrated, in FIG. 11, the user has peeked behind toview the location for the previous navigation instruction and theprevious section of the route only. However, the navigation applicationof some embodiments allows the user to peek behind to view as many pastnavigation instructions and sections of the route as possible all theway back to the first navigation instruction of the route. In suchcases, the navigation application performs zooming, rotating and panningto display the current location and all the locations for all theprevious navigation instructions in the screen together.

D. Responding to Touch Movement

FIG. 12 conceptually illustrates a process 1200 that the navigationapplication in the driving mode performs to present the navigation viewfor the current navigation instruction of a route and a peek view forthe previous or next navigation instruction of the route. The navigationapplication of some embodiments performs the process 1200 on a devicethat has a touch-sensitive screen and/or a near-touch sensitive screenthat displays the output of the navigation application. The process 1200starts when the navigation application is presenting a map view for theroute being traveled by a user.

The process 1200 begins by determining (at 1205) whether the user istouching the screen of the device using two or more fingers. In someembodiments, the process 1200 determines whether the user is touchingthe screen based on the information (e.g., information whether thescreen is being touched, coordinates of the touch(as) if the user istouching the screen at one or more locations of the screen, etc.) from atouch interface of the device. When the process 1200 determines (at1205) that the user is not touching the screen, the process 1200proceeds to 1260, which is described further below.

When the process 1200 determines (at 1205) that the user is touching thescreen using two or more fingers (i.e., a multi-touch), the process 1200identifies (at 1210) the locations of the touches on the screen. In someembodiments, the process 1200 identifies the locations of the touches onthe screen from the information received from the touch interface of thedevice.

Next, the process 1200 determines (at 1215) whether the multi-touch hasmoved on the screen. In some embodiments, the process 1200 takes anaverage coordinates of the touches in the multi-touch to measure themovement. In other embodiments, the process 1200 selects one of thetouches to measure the movement. In some embodiments, the process 1200keeps track of the locations of the touches while the touches aremaintained with the screen. The process 1200 determines that the touchesare moving on the screen when the locations of the touches are changingwhile the touches are maintained.

When the process 1200 determines (at 1215) that the touches have notmoved on the screen, the process 1200 loops back to 1205 to checkwhether all of the touches are maintained. with the screen. When theprocess 1200 determines (at 1215) that the touches have moved on thescreen, the process 1200 identifies (at 1220) the length and thedirection of the movement that the touches have made. In someembodiments, the process 1200 identifies a vector on the coordinatesystem of the screen that represents the movement of the touches andidentifies only the vertical component (e.g., a y-component) of thevector as the length of the movement. In some such embodiments, theprocess 1200 identifies the length of the vertical component of thevector as zero when the vector is not substantially parallel to avertical line on the screen's coordinate system (e.g., not within 40degrees with respect to a vertical line of the screen). That is, theprocess 1200 ignores the movement of the touches if the movement is notconsidered a vertical multi-touch swipe on the screen.

The process 1200 then determines (at 1225) whether the movement of thetouches is in a first direction (e.g., to the top side of the screen).As mentioned above, the process 1200 of some embodiments considers onlythe vertical component of the vector that represents the movement. Theprocess 1200 of these embodiments determines whether the movement of thetouches is in the first direction based on the direction of the verticalcomponent of the vector.

When the process 1200 determines (at 1225) that the movement of thetouches is not in the first direction, the process 1200 proceeds to1235, which is described further below. When the process 1200 determines(at 1225) that the movement of the touches is in the first direction,the process at 1230 slides out the banner and slides in another bannerthat displays the next navigation instruction of the route. The process1200 slides out the banner by a length that is proportional to thelength of the movement of the touches. As the process 1200 slide out thebanner, the process 1200 also modifies (at 1240) the map view to displaya peek view for peeking ahead the next navigation instruction. Theprocess in some embodiments modifies the map view by rotating, zoomingand/or panning the map view such that (1) a vector, from the currentlocation of the user to the location of the next navigation instruction(i.e., the end of the section of the route for the next navigationinstruction), points to the top side of the screen and (2) both thecurrent position of the user and the location for the next navigationinstruction are displayed in the screen together. The process thenproceeds to 1255, which is described further below.

When the process 1200 determines (at 1225) that the movement of thetouches is not in the first direction, the process 1200 determines (at1235) whether the movement of the touches is in the second direction. Insome embodiments, the first and second directions are the oppositedirections to each other. When the process 1200 determines (at 1235)that the movement of the touches is not in the second direction, themovement of the touches is neither in the first direction nor in thesecond direction. That is, the movement is deemed to have a zero lengthor is not considered as a vertical movement. In such cases, the process1200 loops back to 1205 to check whether all of the touches aremaintained with the screen.

When the process 1200 determines (at 1235) that the movement of thetouches is in the second direction, the process at 1245 slides out thebanner and slides in another banner that displays the previousnavigation instruction of the route. The process 1200 slides out thebanner by a length that is proportional to the length of the movement ofthe touches. As the process 1200 slide out the banner, the process 1200also modifies (at 1250) the map view to display a peek view for peekingbehind.

The process in some embodiments modifies the map view by rotating,zooming and/or panning the map view such that (1) a vector, from thebeginning of the section of the route for the previous navigationinstruction to the current location of the user, points to the top sideof the screen and (2) both the current position of the user and thebeginning of the section for the previous navigation instruction aredisplayed in the screen together. The process in other embodimentsmodifies the map view by rotating, zooming and/or panning the map viewsuch that (1) a vector, from the location for the previous navigationinstruction to the current location of the user, points to the top sideof the screen and (2) both the current position of the user and thelocation for the previous navigation instruction are displayed in thescreen together.

The process then determines (at 1255) whether the banner displaying thecurrent navigation instruction has been slid out of the screen. When theprocess determines (at 1255) that the banner has not been slid out ofthe screen, the process loops back to 1205 to check whether the touchesare maintained with the screen. Otherwise the process ends.

When the process 1200 determines (at 1205) that the user is not touchingthe screen using two or more fingers, the process 1200 of someembodiments determines (at 1260) whether a peek view is being displayedin the screen. That is, the process 1200 determines whether the processhas rotated, zoomed out, and/or panned the map view for the next orprevious navigation instruction. When the process determines (at 1260)that the peek view is being displayed, the process bounces back to thenavigation view from the current navigation instruction. This is becausethe touches are no longer maintained and the process of some embodimentsbounces back to the navigation view from the peek view when the touchesare not maintained. When the process 1200 determines (at 1260) that thepeek view is not being displayed, the process 1200 loops back to 1205 tocheck whether the user touches the screen.

E. Automatically Reverting to Navigation View

FIG. 13 illustrates that the navigation application of some embodimentsbacks out from a peek view for the next navigation instruction of aroute being traveled by a user and automatically reverts to a navigationview for the current navigation instruction of the route. Specifically,this figure illustrates in five stages 1305-1325 that the navigationinstruction presenting the map view in the driving mode automaticallyreverts to the navigation view when the user moves close to or arrivesat a location for the current navigation instruction.

The first and second stages 1305 and 1310 are similar to the first andsecond stages 1005 and 1010 described above by reference to FIG. 10.That is, at the first and second stages 1305 and 1310, the navigationapplication has moved a banner 1330, which displays the currentnavigation instruction for the current location of the user, a half wayout to the left side of the screen. At the second stage 1310, thenavigation application displays a partial peek view for the nextnavigation instruction.

At the third stage 1315, like at the third stage 1015 of FIG. 10, thenavigation instruction displays the full peek view for the nextnavigation instruction in 3D. However, in contrast to the navigationapplication of sonic embodiments at the third stage 1015 of FIG. 10, thenavigation application of some embodiments at the third stage 1315 doesnot start restoring the navigation view for the current navigationinstruction even if the touches are not maintained with the screen. Thenavigation application of these embodiments keeps the peek view for thenext instruction even if the touches are not maintained. Moreover, thenavigation application of some of these embodiments updates the positionof the current position indicator (e.g., a puck 1345) in the peek view.

The fourth stage 1320 shows that the navigation application stilldisplays the peek view for the next navigation instruction. The user hasmoved closer to the location for the right turn as indicated by theposition of the puck 1345 in the map that is closer to the junction ofthe Union Street and the B Street than the position of the puck 1345 wasat the previous stage 1315. In some embodiments, the navigationinstruction notifies the user of an imminent turn when the position ofthe user falls within a threshold distance from the location for theturn. For instance, the navigation application of some embodiments atthe fourth stage 1320 presents a short audible notification (e.g., ashort audible sound such as “dong”) to the user to notify the user ofthe imminent turn. In some embodiments, the navigation application usesdifferent short audible notifications for different directions of turns.For instance, the notification uses “ding” for one of the left turn orthe right turn and “long” for the other directional turn.

Moreover, in some embodiments, the navigation application in the drivingmode uses different threshold distance based on the speed of the carthat the user is driving. That is, in some embodiments, the navigationapplication uses a longer threshold distance (e.g., a mile) when theuser moves fast (e.g., at 60 miles per hour) and a shorter thresholddistance (e.g., 500 feet) when the user moves relatively slowly (e.g.,at 20 miles per hour). This is because the navigation application ofthese embodiments differentiates between a highway driving condition anda city driving condition.

When the user reaches the location for the current navigationinstruction, the navigation application of some embodimentsautomatically reverts back to the navigation view for the currentnavigation instruction. As shown at the fifth stage 1325, the navigationapplication reverts to the navigation view for the current navigationinstruction as the user arrives at the location for the right turn ontothe B Street. The navigation application of some embodiments alsoupdates the content displayed on the banner 1330 for the currentnavigation instruction. For instance, as shown, the navigationapplication does not display the remaining distance to the location ofthe turn because the user has reached the location for the turn.

FIG. 14 illustrates another situation in which the navigationapplication of some embodiments automatically reverts to the navigationview for the current navigation instruction of a route from the peekview for the next navigation instruction of the route. Specifically,this figure illustrates in terms of five stages 1405-1425 that thenavigation application backs out from the peek view and automaticallyreverts to the navigation view when a defined period of time elapses.This figures also conceptually illustrates a clock after each of thefirst four stages 1405-1420 to indicate the time at which the stageends.

At the first stage 1405, the navigation application displays a banner1430 that displays the current navigation instruction of a route beingtraveled by a user. The map view is displayed in 3D as the navigationapplication is in the driving mode. The user starts swiping up thescreen using two fingers. The navigation application advances to thenext stage 1410 at 12:15 PM as indicated by the clock depicted betweenthe stages 1405 and 1410.

The second stage 1410 shows that the user has moved up the fingers whilemaintaining the touches with the screen. In response, the navigationapplication has slid the banner 1430 a half way out to the left side ofthe screen and has slid a banner 1435, which shows the next navigationinstruction of the route, a half way into the screen from the right sideof the screen. The navigation application displays a partial peek viewin 3D for the next navigation instruction because the banner 1430 hasbeen slid out only a half a way. The navigation application advances tothe next stage 1415 at 12:15 PM as indicated by the clock depictedbetween the stages 1410 and 1415.

At the third stage 1415, the navigation instruction displays the fullpeek view in 3D for the next navigation instruction. The banner 1435displaying the next navigation instruction is fully displayed as thebanner 1430 displaying the current navigation is completely slid out ofthe screen. The navigation application advances to the next stage 1420at around 12:25 PM as indicated by the clock depicted between the stages1415 and 1420.

The fourth stage 1420 shows that the navigation application stilldisplays the peek view for the next navigation instruction. The user hasnot moved from the position at which the user was at the previous stage1415. The user stops moving and maintains the position as indicated bythe current position indicator 1440. The navigation application advancesto the next stage 1425 at around 12:29 PM as indicated by the clockdepicted between the stages 1420 and 1425.

As mentioned above, the navigation application of some embodimentsreverts to the navigation view for the current navigation instructionfrom the peek view for the future or past navigation instructions when adefined period of time elapses while the navigation application isdisplaying the peek view. In some embodiments, this period of time inthe driving mode is set to a period of time (e.g., one minute) that ismuch shorter than the period of time to revert to the navigation view inthe pedestrian mode. The fifth stage 1425 shows that the navigationapplication of some embodiments has reverted back to the 3D navigationview for the current navigation instruction because more than thedefined period of time is lapsed (e.g., from 12:25PM to 12:29PM) whilethe navigation application displays the peek view.

III. Software Architecture

FIG. 15 illustrates example architecture of a navigation applicationthat allows the user to peek ahead and behind a route. In this example,a navigation application 1500 of some embodiments runs in a device 1505.As shown, the navigation application 1500 includes a touch interface1510, a GUI manger 1515, a virtual camera manager 1520, a renderingmodule 1525, a route manager 1530, and a route generator 1535. Thisfigure also illustrates a map server 1540 and a route server 1545.

The device 1505 of some embodiments has a touch-sensitive screen (notshown)and/or near-touch sensitive screen (not shown) that displays theoutput of the navigation application 1500. The device 1505 alsofacilitates the interaction between the navigation application and themap server 1540 and the route server 1545. In this figure, the device'sown hardware and software architecture is not depicted for thesimplicity of description and illustration. More details about a deviceon which the navigation application may execute will be describedfurther below by reference to FIG. 16.

The map server 1540 is a remote server that provides map data to thenavigation application 1500 that describes relative locations ofstreets, highways, points of interest, etc., in the map per thenavigation application 1500's request. The map data contains 2D and 3Dmap data at different zoom levels and perspectives.

The route server 1545 is a remote server that provides route data to thenavigation application 1500 upon request. In some embodiments, thenavigation application 1500 sends information about a starting locationand a destination location to the router server 1545. The route server1545 of some embodiments computes a set of routes for different modes oftransportation and returns the routes to the navigation application1500.

The route manager 1530 of the navigation application receivesinformation about starting and destination locations and sends theinformation to the router server 1545 or to the route generator 1535 toobtain routes that includes sets of navigation instructions. In someembodiments, the route manager 1530 receives the information from theuser through the GUI manager 1515, which receives user selection/orspecification through GUI items that the GUI manager 1515 manages. Theroute manager 1530 of some embodiments uses one or both of the routegenerator 1535 and the route server 1545 to obtain the routes. Therouter manager 1530 of some embodiments also makes the default selectionof a route and keeps track of the default mode of transportation.

The route generator 1535 generates routes based on the information aboutthe starting and ending locations from the route manager. The routegenerator 1535 is a local equivalent of the route server 1545. The routegenerator 1535 is part of the navigation application 1500 in someembodiments. In some embodiments, however, the route generator 1535 is astand-alone application that executes on the device 1505.

The touch interface 1510 receives the user's interaction with the screen(not shown) of the device 1505. In some embodiments, the touch interface1510 receives touch information (e.g., coordinates of the part of thescreen that sensed a touch). The touch interface 1510 analyzes theinformation and determines whether the information can be interpretedmeaningful gestures such vertical/horizontal swipes, whether there hasbeen a multi-touch, etc. The touch interface 1510 sends the analysis ofthe touch information to the virtual camera manager 1520 and/or the GUImanager 1515.

The GUI manager 1515 manages a set of GUI items. The GUI managerreceives the analysis of the touch information from the touch interface1510 and determines whether the analysis affects any of the GUI itemsthat the GUI manager 1515 manages. For instance, when the touchinterface informs that a touch is moving on the display area, the GUImanager determines whether the touch is on a banner showing a navigationinstruction and moves the banner accordingly if the touch is on thebanner. The GUI manager 1515 informs the virtual camera manager 1520 ofthe movements of the banner.

The GUI manager 1515 also interacts with the route manager 1530. Asmentioned above, the GUI manager 1515 provides the route manager withthe user-specified information about routes to generate. The GUI manager1515 also requests and receives navigation instructions and generatesrendering instructions for drawing banners in the display area. The GUIpasses the rendering instructions to the rendering module 1525 so thatthe rendering module 1525 renders the banner in the display area. TheGUI manager 1515 generates rendering instructions for drawing other GUIitems (e.g., an end control, a list control, route selection banners,etc.) in the display area. The GUI manager 1515 also generates renderinginstructions based on the user's interaction with the GUI items.

The virtual camera manager 1520 receives information about the movementof banners from the GUI manger 1515 and translates them into a movementof the virtual camera. This movement of virtual camera includesinstructions for zooming, rotating, and/or panning instructions. Thevirtual camera manager 1520 sends these instructions to the renderingmodule so that the rendering module can draw the changing map views inthe display area.

In some embodiments, the virtual camera manager receive the analysis ofthe touch input from the touch interface 1510 and moves the virtualcamera accordingly. In these embodiments, the virtual camera manager1510 informs the GUI manager 1515 so that the GUI manager 1515 candetermine whether any of the GUI items that the GUI manager are affectedby the movement of the virtual camera.

The rendering module 1525 receives rendering instructions from the GUImanager 1515, the virtual camera manager 1520, and/or the route manager1530. The rendering module 1525 also obtains map data from the mapserver 1540. The rendering module 1525 draws map views, routes, GUIitems, etc. according to the instructions and map data.

IV. Electronic System

Many of the above-described features and applications are implemented assoftware processes that are specified as a set of instructions recordedon a computer readable storage medium (also referred to as computerreadable medium). When these instructions are executed by one or morecomputational or processing unit)s) (e.g., one or more processors, coresof processors, or other processing units), they cause the processingunit(s) to perform the actions indicated in the instructions. Examplesof computer readable media include, but are not limited to, CD-ROMs,flash drives, random access memory (RAM) chips, hard drives, erasableprogrammable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), etc. The computer readablemedia does not include carrier waves and electronic signals passingwirelessly or over wired connections.

In this specification, the term “software” is meant to include firmwareresiding in read-only memory or applications stored in magnetic storagewhich can be read into memory for processing by a processor. Also, insome embodiments, multiple software inventions can be implemented assub-parts of a larger program while remaining distinct softwareinventions. In some embodiments, multiple software inventions can alsobe implemented as separate programs. Finally, any combination ofseparate programs that together implement a software invention describedhere is within the scope of the invention. In some embodiments, thesoftware programs, when installed to operate on one or more electronicsystems, define one or more specific machine implementations thatexecute and perform the operations of the software programs.

A. Mobile Device

The mapping and navigation applications of some embodiments operate onmobile devices, such as smart phones (e.g., iPhones●) and tablets (e.g.,iPads●). FIG. 16 is an example of an architecture 1600 of such a mobilecomputing device. Examples of mobile computing devices includesmartphones, tablets, laptops, etc. As shown, the mobile computingdevice 1600 includes one or more processing units 1605, a memoryinterface 1610 and a peripherals interface 1615.

The peripherals interface 1615 is coupled to various sensors andsubsystems, including a camera subsystem 1620, a wireless communicationsubsystem(s) 1625, an audio subsystem 1630, an I/O subsystem 1635, etc.The peripherals interface 1615 enables communication between theprocessing units 1605 and various peripherals. For example, anorientation sensor 1645 (e.g., a gyroscope) and an acceleration sensor1650 (e.g., an accelerometer) is coupled to the peripherals interface1615 to facilitate orientation and acceleration functions.

The camera subsystem 1620 is coupled to one or more optical sensors 1640(e.g., a charged coupled device (CCD) optical sensor, a complementarymetal-oxide-semiconductor (CMOS) optical sensor, etc.). The camerasubsystem 1620 coupled with the optical sensors 1640 facilitates camerafunctions, such as image and/or video data capturing. The wirelesscommunication subsystem 1625 serves to facilitate communicationfunctions. In some embodiments, the wireless communication subsystem1625 includes radio frequency receivers and transmitters, and opticalreceivers and transmitters (not shown in FIG. 16) These receivers andtransmitters of some embodiments are implemented to operate over one ormore communication networks such as a GSM network, a Wi-Fi network, aBluetooth network, etc. The audio subsystem 1630 is coupled to a speakerto output audio (e.g., to output voice navigation instructions).Additionally, the audio subsystem 1630 is coupled to a microphone tofacilitate voice-enabled functions, such as voice recognition (e.g., forsearching), digital recording, etc.

The I/O subsystem 1635 involves he transfer between input/outputperipheral devices, such as a display, a touch screen, etc., and thedata bus of the processing units 1605 through the peripherals interface1615. The I/O subsystem 1635 includes a touch-screen controller 1655 andother input controllers 1660 to facilitate the transfer betweeninput/output peripheral devices and the data bus of the processing units1605. As shown, the touch-screen controller 1655 is coupled to a touchscreen 1665. The touch-screen controller 1655 detects contact andmovement on the touch screen 1665 using any of multiple touchsensitivity technologies. The other input controllers 1660 are coupledto other input/control devices, such as one or more buttons. Someembodiments include a near-touch sensitive screen and a correspondingcontroller that can detect near-touch interactions instead of or inaddition to touch interactions.

The memory interface 1610 is coupled to memory 1670. In someembodiments, the memory 1670 includes volatile memory (e.g., high-speedrandom access memory), non-volatile memory (e.g., flash memory), acombination of volatile and non-volatile memory, and/or any other typeof memory. As illustrated in FIG. 16, the memory 1670 stores anoperating system (OS) 1672. The OS 1672 includes instructions forhandling basic system services and for performing hardware dependenttasks.

The memory 1670 also includes communication instructions 1674 tofacilitate communicating with one or more additional devices; graphicaluser interface instructions 1676 to facilitate graphic user interfaceprocessing; image processing instructions 1678 to facilitateimage-related processing and functions; input processing instructions1680 to facilitate input-related (e.g., touch input) processes andfunctions; audio processing instructions 1682 to facilitateaudio-related processes and functions; and camera instructions 1684 tofacilitate camera-related processes and functions. The instructionsdescribed above are merely exemplary and the memory 1670 includesadditional and/or other instructions in some embodiments. For instance,the memory for a smartphone may include phone instructions to facilitatephone-related processes and functions. Additionally, the memory mayinclude instructions for a mapping and navigation application as well asother applications. The above-identified instructions need not beimplemented as separate software programs or modules. Various functionsof the mobile computing device can be implemented in hardware and/or insoftware, including in one or more signal processing and/or applicationspecific integrated circuits.

While the components illustrated in FIG. 16 are shown as separatecomponents, one of ordinary skill in the art will recognize that two ormore components may be integrated into one or more integrated circuits.In addition, two or more components may be coupled together by one ormore communication buses or signal lines. Also, while many of thefunctions have been described as being performed by one component, oneof ordinary skill in the art will realize that the functions describedwith respect to FIG. 16 may be split into two or more integratedcircuits.

B. Electronic System

FIG. 17 conceptually illustrates another example of an electronic system1700 with which some embodiments of the invention are implemented. Theelectronic system 1700 may be a computer (e.g., a desktop computer,personal computer, tablet computer, etc.), phone, PDA, or any other sortof electronic or computing device. Such an electronic system includesvarious types of computer readable media and interfaces for variousother types of computer readable media. Electronic system 1700 includesa bus 1705, processing unit(s) 1710, a graphics processing unit (GPU)1715, a system memory 1720, a network 1725, a read-only memory 1730, apermanent storage device 1735, input devices 1740, and output devices1745.

The bus 1705 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of theelectronic system 1700. For instance, the bus 1705 communicativelyconnects the processing unit(s) 1710 with the read-only memory 1730, theGPU 1715, the system memory 1720, and the permanent storage device 1735.

From these various memory units, the processing unit(s) 1710 retrievesinstructions to execute and data to process in order to execute theprocesses of the invention. The processing unit(s) may be a singleprocessor or a multi-core processor in different embodiments. Someinstructions are passed to and executed by the GPU 1715. The GPU 1715can offload various computations or complement the image processingprovided by the processing unit(s) 1710. In some embodiments, suchfunctionality can be provided using Corelmage's kernel shading language.

The read-only-memory (ROM) 1730 stores static data and instructions thatare needed by the processing unit(s) 1710 and other modules of theelectronic system. The permanent storage device 1735, on the other hand,is a read-and-write memory device. This device is a non-volatile memoryunit that stores instructions and data even when the electronic system1700 is off. Some embodiments of the invention use a mass-storage device(such as a magnetic or optical disk and its corresponding disk drive,integrated flash memory) as the permanent storage device 1735.

Other embodiments use a removable storage device (such as a floppy disk,flash memory device, etc., and its corresponding drive) as the permanentstorage device. Like the permanent storage device 1735, the systemmemory 1720 is a read-and-write memory device. However, unlike storagedevice 1735, the system memory 1720 is a volatile read-and-write memory,such a random access memory. The system memory 1720 stores some of theinstructions and data that the processor needs at runtime. In someembodiments, the invention's processes are stored in the system memory1720, the permanent storage device 1735, and/or the read-only memory1730. For example, the various memory units include instructions forprocessing multimedia clips in accordance with some embodiments. Fromthese various memory units, the processing unit(s) 1710 retrievesinstructions to execute and data to process in order to execute theprocesses of some embodiments.

The bus 1705 also connects to the input and output devices 1740 and1745. The input devices 1740 enable the user to communicate informationand select commands to the electronic system. The input devices 1740include alphanumeric keyboards and pointing devices (also called “cursorcontrol devices”), cameras (e.g., webcams), microphones or similardevices for receiving voice commands, etc. The output devices 1745display images generated by the electronic system or otherwise outputdata. The output devices 1745 include printers and display devices, suchas cathode ray tubes (CRT) or liquid crystal displays (LCD), as well asspeakers or similar audio output devices. Some embodiments includedevices such as a touchscreen that function as both input and outputdevices.

Finally, as shown in FIG. 17, bus 1705 also couples electronic system1700 to a network 1725 through a network adapter (not shown). In thismanner, the computer can be a part of a network of computers (such as alocal area network (“LAN”), a wide area network (“WAN”), or anIntranet), or a network of networks, such as the Internet. Any or allcomponents of electronic system 1700 may be used in conjunction with theinvention.

Some embodiments include electronic components, such as microprocessors,storage and memory that store computer program instructions in amachine-readable or computer-readable medium (alternatively referred toas computer-readable storage media, machine-readable media, ormachine-readable storage media). Some examples of such computer-readablemedia include RAM, ROM, read-only compact discs (CD-ROM), recordablecompact discs (CD-R), rewritable compact discs (CD-RW), read-onlydigital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a varietyof recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.),flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.),magnetic and/or solid state hard drives, read-only and recordableBlu-Ray● discs, ultra density optical discs, any other optical ormagnetic media, and floppy disks. The computer-readable media may storea computer program that is executable by at least one processing unitand includes sets of instructions for performing various operations.Examples of computer programs or computer code include machine code,such as is produced by a compiler, and files including higher-level codethat are executed by a computer, an electronic component, or amicroprocessor using an interpreter.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, some embodiments areperformed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In some embodiments, such integrated circuits executeinstructions that are stored on the circuit itself. In addition, someembodiments execute software stored in programmable logic devices(PLDs), ROM, or RAM devices.

As used in this specification. and any claims of this application, theterms “computer”, “server”, “processor”, and “memory” all refer toelectronic or other technological devices. These terms exclude people orgroups of people. For the purposes of the specification, the termsdisplay or displaying means displaying on an electronic device. As usedin this specification and any claims of this application, the terms“computer readable medium,” “computer readable media,” and “machinereadable medium” are entirely restricted to tangible, physical objectsthat store information in a form that is readable by a computer. Theseterms exclude any wireless signals, wired download signals, and anyother ephemeral signals.

V. Map Service Environment

Various embodiments may operate within a map service operatingenvironment. FIG. 18 illustrates a map service operating environment,according to some embodiments. A map service 1830 (also referred to asmapping service) may provide map services for one or more client devices1802 a-1802 c in communication with the map service 1830 through variouscommunication methods and protocols. A map service 1830 in someembodiments provides map information and other map-related data, such astwo-dimensional map image data (e.g., aerial view of roads utilizingsatellite imagery), three-dimensional map image data (e.g., traversablemap with three-dimensional features, such as buildings), route anddirection calculations (e.g., ferry route calculations or directionsbetween two points for a pedestrian), real-time navigation data (e.g.,turn-by-turn visual navigation data in two or three dimensions),location data (e.g., where the client device is currently located), andother geographic data (e.g., wireless network coverage, weather, trafficinformation, or nearby points-of-interest). In various embodiments, themap service data may include localized labels for different countries orregions. Localized labels may be utilized to present map labels (e.g.,street names, city names, points of interest) in different languages onclient devices. Client devices 1802 a-1802 c may utilize these mapservices by obtaining map service data. Client devices 1802 a-1802 c mayimplement various techniques to process map service data. Client devices1802 a-1802 c may then provide map services to various entities,including, but not limited to, users, internal software or hardwaremodules, and/or other systems or devices external to the client devices1802 a-1802 c.

In some embodiments, a map service is implemented by one or more nodesin a distributed computing system. Each node may be assigned one or moreservices or components of a map service. Some nodes may be assigned thesame map service or component of a map service. A load balancing node insome embodiments distributes access or requests to other nodes within amap service. In some embodiments a map service is implemented as asingle system, such as a single server. Different modules or hardwaredevices within a server may implement one or more of the variousservices provided by a map service.

A map service in some embodiments provides map services by generatingmap service data in various formats. In some embodiments, one format ofmap service data is map image data. Map image data provides image datato a client device so that the client device may process the image data(e.g., rendering and/or displaying the image data as a two-dimensionalor three-dimensional map). Map image data, whether in two or threedimensions, may specify one or more map tiles. A map tile may be aportion of a larger map image. Assembling together the map tiles of amap produces the original map. Tiles may be generated from map imagedata, routing or navigation data, or any other map service data. In someembodiments map tiles are raster-based map tiles, with tile sizesranging from any size both larger and smaller than a commonly-used 256pixel by 256 pixel tile. Raster-based map tiles may be encoded in anynumber of standard digital image representations including, but notlimited to, Bitmap (.bmp), Graphics Interchange Format (.gif), JointPhotographic Experts Group (.jpg, .jpeg, etc.), Portable NetworksGraphic (.png), or Tagged Image File Format (.tiff). In someembodiments, map tiles are vector-based map tiles, encoded using vectorgraphics, including, but not limited to, Scalable Vector Graphics (.svg)or a Drawing File (.drw). Some embodiments also include tiles with acombination of vector and raster data. Metadata or other informationpertaining to the map tile may also be included within or along with amap tile, providing further map service data to a client device. Invarious embodiments, a map tile is encoded for transport utilizingvarious standards and/or protocols, some of which are described inexamples below.

In various embodiments, map tiles may be constructed from image data ofdifferent resolutions depending on zoom level. For instance, for lowzoom level (e.g., world or globe view), the resolution of map or imagedata need not be as high relative to the resolution at a high zoom level(e.g., city or street level). For example, when in a globe view, theremay be no need to render street level artifacts as such objects would beso small as to be negligible in many cases.

A map service in some embodiments performs various techniques to analyzea map tile before encoding the tile for transport. This analysis mayoptimize map service performance for both client devices and a mapservice. In some embodiments map tiles are analyzed for complexity,according to vector-based graphic techniques, and constructed utilizingcomplex and non-complex layers. Map tiles may also be analyzed forcommon image data or patterns that may be rendered as image textures andconstructed by relying on image masks. In some embodiments, raster-basedimage data in a map tile contains certain mask values, which areassociated with one or more textures. Some embodiments also analyze maptiles for specified features that may be associated with certain mapstyles that contain style identifiers.

Other map services generate map service data relying upon various dataformats separate from a map tile in some embodiments. For instance, mapservices that provide location data may utilize data formats conformingto location service protocols, such as, but not limited to, RadioResource Location services Protocol (RRLP), TIA 801 for Code DivisionMultiple Access (CDMA), Radio Resource Control (RRC) position protocol,or LTE Positioning Protocol (LPP). Embodiments may also receive orrequest data from client devices identifying device capabilities orattributes (e.g., hardware specifications or operating system version)or communication capabilities (e.g., device communication bandwidth asdetermined by wireless signal strength or wire or wireless networktype).

A map service may obtain map service data from internal or externalsources. For example, satellite imagery used in map image data may beobtained from external services, or internal systems, storage devices,or nodes. Other examples may include, but are not limited to, GPSassistance servers, wireless network coverage databases, business orpersonal directories, weather data, government information (e.g.,construction updates or road name changes), or traffic reports. Someembodiments of a map service may update map service data (e.g., wirelessnetwork coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client devicerequests for map services. These requests may be for a specific maps orportions of a map. Some embodiments format requests for a map asrequests for certain map tiles. In some embodiments, requests alsosupply the map service with starting locations (or current locations)and destination locations for a route calculation. A client device mayalso request map service rendering information, such as map textures orstyle sheets. In at least some embodiments, requests are also one of aseries of requests implementing turn-by-turn navigation. Requests forother geographic data may include, but are not limited to, requests forcurrent location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

A map service, in some embodiments, analyzes client device requests tooptimize a device or map service operation. For instance, a map servicemay recognize that the location of a client device is in an area of poorcommunications (e.g., weak wireless signal) and send more map servicedata to supply a client device in the event of loss in communication orsend instructions to utilize different client hardware (e.g.,orientation sensors) or software (e.g., utilize wireless locationservices or Wi-Fi positioning instead of GPS-based services). In anotherexample, a map service may analyze a client device request forvector-based map image data and determine that raster-based map databetter optimizes the map image data according to the image's complexity.Embodiments of other map services may perform similar analysis on clientdevice requests and, as such, the above examples are not intended to belimiting.

Various embodiments of client devices (e.g., client devices 1802 a-1802c) are implemented on different portable-multifunction device types.Client devices 1802 a-1802 c utilize map service 1830 through variouscommunication methods and protocols. In some embodiments, client devices1802 a-1802 c obtain map service data from map service 1830. Clientdevices 1802 a-1802 c request or receive map service data. Clientdevices 1802 a-1802 c then process map service data (e.g., render and/ordisplay the data) and may send the data to another software or hardwaremodule on the device or to an external device or system.

A client device, according to some embodiments, implements techniques torender and/or display maps. These maps may be requested or received invarious formats, such as map tiles described above. A client device mayrender a map in two-dimensional or three-dimensional views. Someembodiments of a client device display a rendered map and allow a user,system, or device providing input to manipulate a virtual camera in themap, changing the map display according to the virtual camera'sposition, orientation, and field-of-view. Various forms and inputdevices are implemented to manipulate a virtual camera. In someembodiments, touch input, through certain single or combination gestures(e.g., touch-and-hold or a swipe) manipulate the virtual camera. Otherembodiments allow manipulation of the device's physical location tomanipulate a virtual camera. For instance, a client device may be tiltedup from its current position to manipulate the virtual camera to rotateup. In another example, a client device may be tilted forward from itscurrent position to move the virtual camera forward. Other input devicesto the client device may be implemented including, but not limited to,auditory input (e.g., spoken words), a physical keyboard, mouse, and/ora joystick.

Some embodiments provide various visual feedback to virtual cameramanipulations, such as displaying an animation of possible virtualcamera manipulations when transitioning from two-dimensional map viewsto three-dimensional map views. Some embodiments also allow input toselect a map feature or object (e.g., a building) and highlight theobject, producing a blur effect that maintains the virtual camera'sperception of three-dimensional space.

In some embodiments, a client device implements a navigation system(e.g., turn-by-turn navigation). A navigation system provides directionsor route information, which may be displayed to a user. Some embodimentsof a client device request directions or a route calculation from a mapservice. A client device may receive map image data and route data froma map service. In some embodiments, a client device implements aturn-by-turn navigation system, which provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as a Global Positioning Satellite (GPS). A client device maydisplay map image data that reflects the current location of the clientdevice and update the map image data in real-time. A navigation systemmay provide auditory or visual directions to follow a certain route.

A virtual camera is implemented to manipulate navigation map dataaccording to some embodiments. In some embodiments, the client devicesallow the device to adjust the virtual camera display orientation tobias toward the route destination. Some embodiments also allow thevirtual camera to navigate turns by simulating the inertial motion ofthe virtual camera.

Client devices implement various techniques to utilize map service datafrom map service. Some embodiments implement some techniques to optimizerendering of two-dimensional and three-dimensional map image data. Insome embodiments, a client device locally stores rendering information.For instance, a client stores a style sheet, which provides renderingdirections for image data containing style identifiers. In anotherexample, common image textures may be stored to decrease the amount ofmap image data transferred from a map service. Client devices indifferent embodiments implement various modeling techniques to rendertwo-dimensional and three-dimensional map image data, examples of whichinclude, but are not limited to: generating three-dimensional buildingsout of two-dimensional building footprint data; modeling two-dimensionaland three-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data. In someembodiments, the client devices also order or prioritize map servicedata in certain techniques. For instance, a client device detects themotion or velocity of a virtual camera, which if exceeding certainthreshold values, lower-detail image data is loaded and rendered forcertain areas. Other examples include: rendering vector-based curves asa series of points, preloading map image data for areas of poorcommunication with a map service, adapting textures based on displayzoom level, or rendering map image data according to complexity.

In some embodiments, client devices communicate utilizing various dataformats separate from a map tile. For instance, some client devicesimplement Assisted Global Positioning Satellites (A-GPS) and communicatewith location services that utilize data formats conforming to locationservice protocols, such as, but not limited to, Radio Resource Locationservices Protocol (RRLP), TIA 801 for Code Division Multiple Access(CDMA), Radio Resource Control (RRC) position protocol, or LTEPositioning Protocol (LPP). Client devices may also receive GPS signalsdirectly. Embodiments may also send data, with or without solicitationfrom a map service, identifying the client device's capabilities orattributes (e.g., hardware specifications or operating system version)or communication capabilities (e.g., device communication bandwidth asdetermined by wireless signal strength or wire or wireless networktype).

FIG. 18 illustrates one possible embodiment of operating environment1800 for a map service 1830 and client devices 1802 a-1802 c, In someembodiments, devices 1802 a, 1802 b, and 1802 c communicate over one ormore wire or wireless networks 1810. For example, wireless network 1810,such as a cellular network, can communicate with a wide area network(WAN) 1820, such as the Internet, by use of gateway 1814. A gateway 1814in some embodiments provides a packet oriented mobile data service, suchas General Packet Radio Service (GPRS), or other mobile data serviceallowing wireless networks to transmit data to other networks, such aswide area network 1820. Likewise, access device 1812 (e.g., IEEE 802.11gwireless access device) provides communication access to WAN 1820.Devices 1802 a and 1802 b can be any portable electronic or computingdevice capable of communicating with a map service. Device 1802 c can beany non-portable electronic or computing device capable of communicatingwith a map service.

In some embodiments, both voice and data communications are establishedover wireless network 1810 and access device 1812. For instance, device1802 a can place and receive phone calls (e.g., using voice overInternet Protocol (VoIP) protocols), send and receive e-mail messages(e.g., using Simple Mail Transfer Protocol (SMTP) or Post OfficeProtocol 3 (POP3)), and retrieve electronic documents and/or streams,such as web pages, photographs, and videos, over wireless network 1810,gateway 1814, and WAN 1820 (e.g., using Transmission ControlProtocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)).Likewise, in some implementations, devices 1802 b and 1802 c can placeand receive phone calls, send and receive e-mail messages, and retrieveelectronic documents over access device 1812 and WAN 1820. In variousembodiments, any of the illustrated client devices may communicate withmap service 1830 and/or other service(s) 1850 using a persistentconnection established in accordance with one or more securityprotocols, such as the Secure Sockets Layer (SSL) protocol or theTransport Layer Security (TLS) protocol.

Devices 1802 a and 1802 b can also establish communications by othermeans. For example, wireless device 1802 a can communicate with otherwireless devices (e.g., other devices 1802 b, cell phones, etc.) overthe wireless network 1810. Likewise devices 1802 a and 1802 b canestablish peer-to-peer communications 1840 (e.g., a personal areanetwork) by use of one or more communication subsystems, such asBluetooth● communication from Bluetooth Special Interest Group, Inc. ofKirkland, Wash. Device 1802 c can also establish peer to peercommunications with devices 1802 a or 1802 b (not shown). Othercommunication protocols and topologies can also be implemented. Devices1802 a and 1802 b may also receive Global Positioning Satellite (GPS)signals from GPS satellites 1860.

Devices 1802 a, 1802 b, and 1802 c can communicate with map service 1830over one or more wired and/or wireless networks, 1812 or 1810. Forinstance, map service 1830 can provide map service data to renderingdevices 1802 a, 1802 b, and 1802 c. Map service 1830 may alsocommunicate with other services 1850 to obtain data to implement mapservices. Map service 1830 and other services 1850 may also receive GPSsignals from GPS satellites 1860.

In various embodiments, map service 1830 and/or other service(s) 1850are configured to process search requests from any of the clientdevices. Search requests may include but are not limited to queries forbusinesses, addresses, residential locations, points of interest, orsome combination thereof. Map service 1830 and/or other service(s) 1850may be configured to return results related to a variety of parametersincluding but not limited to a location entered into an address bar orother text entry field (including abbreviations and/or other shorthandnotation), a current map view (e.g., user may be viewing one location onthe multifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriaincluding but not limited to a quantity of times the search result(e.g., a particular point of interest) has been requested, a measure ofquality associated with the search result (e.g., highest user oreditorial review rating), and/or the volume of reviews for the searchresults (e.g., the number of times the search result has been review orrated).

In various embodiments, map service 1830 and/or other service(s) 1850are configured to provide auto-complete search results that aredisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the Internet) by map service 1830 and/or other service(s) 1850,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device is configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 1830 and/or other service(s) 1850provide one or more feedback mechanisms to receive feedback from clientdevices 1802 a-1802 c. For instance, client devices may provide feedbackon search results to map service 1830 and/or other service(s) 1850(e.g., feedback specifying ratings, reviews, temporary or permanentbusiness closures, errors etc.); this feedback may be used to updateinformation about points of interest in order to provide more accurateor more up-to-date search results in the future. In some embodiments,map service 1830 and/or other service(s) 1850 may provide testinginformation to the client device (e.g., an A/B test) to determine whichsearch results are best. For instance, at random intervals, the clientdevice may receive and present two search results to a user and allowthe user to indicate the best result. The client device may report thetest results to map service 1830 and/or other service(s) 1850 to improvefuture search results based on the chosen testing technique, such as anA/B test technique in which a baseline control sample is compared to avariety of single-variable test samples in order to improve results.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. For instance, many of the figuresillustrate various touch gestures (e.g., taps, double taps, swipegestures, press and hold gestures, etc.). However, many of theillustrated operations could be performed via different touch gestures(e.g., a swipe instead of a tap, etc.) or by non-touch input (e.g.,using a cursor controller, a keyboard, a touchpad/trackpad, a near-touchsensitive screen, etc.). In addition, a number of the figuresconceptually illustrate processes. The specific operations of theseprocesses may not be performed in the exact order shown and described.The specific operations may not be performed in one continuous series ofoperations, and different specific operations may be performed indifferent embodiments. Furthermore, the process could be implementedusing several sub-processes, or as part of a larger macro process. Thus,one of ordinary skill in the art would understand that the invention isnot to be limited by the foregoing illustrative details, but rather isto be defined by the appended claims.

What is claimed is:
 1. A method of presenting navigation instructions onan interface of a mapping application on a device traversing a route,the method comprising: presenting, in a first maneuver banner of themapping application interface, a first navigation instruction for afirst maneuver along the route; presenting the first maneuver in a mapregion of the mapping application interface; receiving a touch inputsliding the first maneuver banner off the screen; in response toreceiving the touch input, presenting a second turn-by-turn navigationinstruction for a second maneuver in a second maneuver banner; andzooming out and rotating the map region to present the second maneuverin the map region.
 2. The method of claim 1, further comprising:receiving a touch input vertically swiping the map region; in responseto the touch input, presenting the second turn-by-turn navigationinstruction for the second maneuver in the second maneuver banner; andpresenting the second maneuver in the map region;
 3. The method of claim2, wherein the touch input vertically swipes the map region upward, andwherein the second maneuver occurs after the first maneuver in theroute.
 4. The method of claim 2, wherein the touch input verticallyswipes the map region downward, further comprising presenting a thirdturn-by-turn navigation instruction for a third maneuver in a thirdmaneuver banner, wherein the third maneuver occurs before the firstmaneuver in the route.
 5. The method of claim 1, further comprising:Identifying a length of the touch input on the first maneuver banner;Determining that the length exceeds a length threshold; and In responseto the determination, presenting the second turn-by-turn navigationinstruction for the second maneuver in the second maneuver banner; andzooming out and rotating the map region to present the second maneuverin the map region.
 6. The method of claim 5, further comprising:identifying a speed of the touch input on the first maneuver banner;determining that the speed exceeds a speed threshold and that the lengthdoes not exceed the length threshold; and in response to thedetermination, presenting the second turn-by-turn navigation instructionfor the second maneuver in the second maneuver banner; and zooming outand rotating the map region to present the second maneuver in the mapregion.
 7. The method of claim 1, further comprising: presenting thesecond turn-by-turn navigation instruction for a second maneuver in thesecond maneuver banner; presenting the second maneuver in the mapregion; determining that the device is approaching a maneuver pointalong the route; and automatically presenting, in the map region of themapping application interface, a current location of the device alongthe route.
 8. A non-transitory machine readable medium for storing amapping application which when executed by at least one processing unitprovides a sequence of turn-by-turn navigation instructions on a displayscreen of a device traversing a route, the mapping applicationcomprising sets of instructions for: presenting, in a first maneuverbanner of the mapping application interface, a first navigationinstruction for a first maneuver along the route; presenting the firstmaneuver in a map region of the mapping application interface; receivinga touch input sliding the first maneuver banner off the screen; inresponse to receiving the touch input, presenting a second turn-by-turnnavigation instruction for a second maneuver in a second maneuverbanner; and zooming out and rotating the map region to present thesecond maneuver in the map region.
 9. The non-transitory machinereadable medium of claim 8, wherein the mapping application furthercomprises sets of instructions for: receiving a touch input verticallyswiping the map region; in response to the touch input, presenting thesecond turn-by-turn navigation instruction for the second maneuver inthe second maneuver banner; and presenting the second maneuver in themap region;
 10. The non-transitory machine readable medium of claim 9,wherein the touch input vertically swipes the map region upward, andwherein the second maneuver occurs after the first maneuver in theroute.
 11. The non-transitory machine readable medium of claim 9,wherein the touch input vertically swipes the map region downward, andwherein the mapping application further comprises sets of instructionsfor presenting a third turn-by-turn navigation instruction for a thirdmaneuver in a third maneuver banner, wherein the third maneuver occursbefore the first maneuver in the route.
 12. The non-transitory machinereadable medium of claim 9 wherein the mapping application furthercomprises sets of instructions for: Identifying a length of the touchinput on the first maneuver banner; Determining that the length exceedsa length threshold; and In response to the determination, presenting thesecond turn-by-turn navigation instruction for the second maneuver inthe second maneuver banner; and zooming out and rotating the map regionto present the second maneuver in the map region.
 13. The non-transitorymachine readable medium of claim 12, wherein the mapping applicationfurther comprises sets of instructions for: identifying a speed of thetouch input on the first maneuver banner; determining that the speedexceeds a speed threshold and that the length does not exceed the lengththreshold; and in response to the determination, presenting the secondturn-by-turn navigation instruction for the second maneuver in thesecond maneuver banner; and zooming out and rotating the map region topresent the second maneuver in the map region.
 14. The non-transitorymachine readable medium of claim 8, wherein the mapping applicationfurther comprises sets of instructions for: presenting the secondturn-by-turn navigation instruction for a second maneuver in the secondmaneuver banner; presenting the second maneuver in the map region;determining that the device is approaching a maneuver point along theroute; and automatically presenting, in the map region of the mappingapplication interface, a current location of the device along the route.15. A mobile device comprising: a set of processing units; anon-transitory computer readable medium storing a program which whenexecuted by the set of processing units provides a sequence ofturn-by-turn navigation instructions on a display screen of a devicetraversing a route, the program comprising sets of instructions for:presenting, in a first maneuver banner of the mapping applicationinterface, a first navigation instruction for a first maneuver along theroute; presenting the first maneuver in a map region of the mappingapplication interface; receiving a touch input sliding the firstmaneuver banner off the screen; in response to receiving the touchinput, presenting a second turn-by-turn navigation instruction for asecond maneuver in a second maneuver banner; and zooming out androtating the map region to present the second maneuver in the mapregion.
 16. The mobile device of claim 15, wherein the program furthercomprises sets of instructions for: receiving a touch input verticallyswiping the map region; in response to the touch input, presenting thesecond turn-by-turn navigation instruction for the second maneuver inthe second maneuver banner; and presenting the second maneuver in themap region;
 17. The mobile device of claim 16, wherein the touch inputvertically swipes the map region upward, and wherein the second maneuveroccurs after the first maneuver in the route.
 18. The mobile device ofclaim 16, wherein the program further comprises sets of instructionsfor: Identifying a length of the touch input on the first maneuverbanner; Determining that the length exceeds a length threshold; and Inresponse to the determination, presenting the second turn-by-turnnavigation instruction for the second maneuver in the second maneuverbanner; and zooming out and rotating the map region to present thesecond maneuver in the map region.
 19. The mobile device of claim 18,wherein the program further comprises sets of instructions for:identifying a speed of the touch input on the first maneuver banner;determining that the speed exceeds a speed threshold and that the lengthdoes not exceed the length threshold; and in response to thedetermination, presenting the second turn-by-turn navigation instructionfor the second maneuver in the second maneuver banner; and zooming outand rotating the map region to present the second maneuver in the mapregion.
 20. The mobile device of claim 15, wherein the program furthercomprises sets of instructions for: presenting the second turn-by-turnnavigation instruction for a second maneuver in the second maneuverbanner; presenting the second maneuver in the map region; determiningthat the device is approaching a maneuver point along the route; andautomatically presenting, in the map region of the mapping applicationinterface, a current location of the device along the route.